geode-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "ASF GitHub Bot (JIRA)" <>
Subject [jira] [Commented] (GEODE-1728) SessionCachingFilter can create multiple sessions when requests are forwarded
Date Tue, 09 May 2017 00:01:04 GMT


ASF GitHub Bot commented on GEODE-1728:

Github user asfgit closed the pull request at:

> SessionCachingFilter can create multiple sessions when requests are forwarded
> -----------------------------------------------------------------------------
>                 Key: GEODE-1728
>                 URL:
>             Project: Geode
>          Issue Type: Bug
>          Components: docs, http session
>            Reporter: Dan Smith
>            Assignee: Karen Smoler Miller
> Our installer adds this configuration to the users web.xml file for the session state
> {code}
> <filter-mapping>
>         <filter-name>gemfire-session-filter</filter-name>
>         <url-pattern>/*</url-pattern>
>         <dispatcher>FORWARD</dispatcher>
>         <dispatcher>INCLUDE</dispatcher>
>         <dispatcher>REQUEST</dispatcher>
>         <dispatcher>ERROR</dispatcher>
>     </filter-mapping>
> {code}
> This means that our filter will be applied to all incoming requests, and it will be applied
*again* if the request is forwarded to or includes another servlet.
> We wrap the HttpServletRequest in our own RequestWrapper class. We have some code that
tries to prevent wrapping a request multiple times:
> {code}
>     /**
>      * Early out if this isn't the right kind of request. We might see a
>      * RequestWrapper instance during a forward or include request.
>      */
>     if (request instanceof RequestWrapper ||
>         !(request instanceof HttpServletRequest)) {
>       LOG.debug("Handling already-wrapped request");
>       chain.doFilter(request, response);
>       return;
>     }
> {code}
> Unfortunately, this check will not work if there are *other* filters in the chain that
also wrap the HttpServletRequest. That can result in us wrapping the forwarded request in
a new RequestWrapper that will create another session.
> We should not add these <dispatcher/> elements to the web.xml; it should  be sufficient
for our filter to intercept all requests initially. In addition, we might want to enhance
our check to see if we have already wrapped a request to follow the chain of wrapped requests
deeper. As long as other filters wrap the request in a subclass of HttpServletRequestWrapper
we should be able to unwrap the request if needed.

This message was sent by Atlassian JIRA

View raw message