过滤器中Session attributes为null问题及Servlet首次响应缓存需求

Let’s dive into why your filter is hitting null session attributes while building your response caching logic, and walk through actionable fixes to get things working:

1. Session Isn’t Initialized Before Filter Execution #

By default, a Servlet session only gets created when your code explicitly calls request.getSession() (or request.getSession(true)). If your filter runs before the target Servlet has a chance to create a session, and you haven’t initialized the session in the filter itself, calling request.getSession(false) (which returns null if no session exists) will leave you with a null session—and thus null attributes.

Fix: #

Explicitly initialize the session in your filter if you need it for tracking:

HttpSession session = request.getSession(true); // Creates a session if none exists
// Now you can safely access session attributes
Boolean isResponseCached = (Boolean) session.getAttribute("isResponseCached");

If you don’t want to create a session unnecessarily (e.g., only check for an existing one), add a null check:

HttpSession session = request.getSession(false);
if (session != null) {
    Boolean isResponseCached = (Boolean) session.getAttribute("isResponseCached");
    // Handle cached logic
} else {
    // No session exists yet—proceed with first-time response capture
}

2. Your Caching Logic Might Not Need Sessions At All #

Wait a second—using session attributes to track cached responses might not be the best fit for your use case. Sessions are user-specific, but if you want to cache the Servlet’s response globally (for all users), using the request’s URI as a cache key is more reliable and avoids session-related issues entirely.

Alternative Approach (No Session Required): #

Generate a unique cache filename based on the request URL instead:

String requestURI = request.getRequestURI();
// Sanitize URI to use as a valid filename
String cacheFileName = requestURI.replaceAll("[^a-zA-Z0-9.-]", "_") + ".cache";
File cacheFile = new File("/your/cache/directory/path", cacheFileName);

if (cacheFile.exists()) {
    // Serve cached response
    try (FileInputStream fis = new FileInputStream(cacheFile)) {
        response.setContentType("text/html"); // Match original content type
        // Copy cached content to response stream (use Apache Commons IO or custom logic)
        byte[] buffer = new byte[1024];
        int bytesRead;
        while ((bytesRead = fis.read(buffer)) != -1) {
            response.getOutputStream().write(buffer, 0, bytesRead);
        }
    }
} else {
    // Capture and cache the first-time response
    HttpServletResponseWrapper wrappedResponse = new HttpServletResponseWrapper((HttpServletResponse) response) {
        private final ByteArrayOutputStream bos = new ByteArrayOutputStream();

        @Override
        public ServletOutputStream getOutputStream() throws IOException {
            return new ServletOutputStream() {
                @Override
                public void write(int b) throws IOException {
                    bos.write(b);
                }

                @Override
                public boolean isReady() {
                    return true;
                }

                @Override
                public void setWriteListener(WriteListener listener) {}
            };
        }

        @Override
        public PrintWriter getWriter() throws IOException {
            return new PrintWriter(new OutputStreamWriter(bos, getCharacterEncoding()));
        }
    };

    // Let the target Servlet process the request
    chain.doFilter(request, wrappedResponse);

    // Write captured response to cache file
    try (FileOutputStream fos = new FileOutputStream(cacheFile)) {
        fos.write(wrappedResponse.bos.toByteArray());
    }

    // Send the captured response to the client
    response.getOutputStream().write(wrappedResponse.bos.toByteArray());
}

This method bypasses session issues entirely and caches the response globally, which is likely what you want for a shared page rendered by your Servlet.

3. Session Tracking Configuration Problems #

If you do need to use sessions, double-check these configurations:

• Ensure client-side cookies are enabled (most apps use cookie-based session tracking by default). If cookies are disabled, implement URL rewriting with response.encodeURL() in your Servlets to pass the session ID.
• Verify your filter mapping (in web.xml or via annotations) correctly targets the requests handled by your target Servlet. A misconfigured mapping could mean the filter runs on requests that never initialize a session.

内容的提问来源于stack exchange，提问作者Manish Bansal