[mod_cluster-issues] [JBoss JIRA] (MODCLUSTER-443) mod_cluster doesn't recognize ; as a proper context delimiter causing 404s on requests with URL jsessionids

[Michal Babacek (JIRA)]

    [ https://issues.jboss.org/browse/MODCLUSTER-443?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13020708#comment-13020708 ] 

Michal Babacek commented on MODCLUSTER-443:
-------------------------------------------

Guys, this is weird. I have a test like this and it passes all right with mod_cluster 1.2.9.Final: https://gist.github.com/Karm/8432a95db8d75ba0d269#file-context_delimiter_snippet-groovy-L8

WDYT? IMHO the user mentioned on the linked Bugzilla has an old mod_cluster.

> mod_cluster doesn't recognize ; as a proper context delimiter causing 404s on requests with URL jsessionids
> -----------------------------------------------------------------------------------------------------------
>
>                 Key: MODCLUSTER-443
>                 URL: https://issues.jboss.org/browse/MODCLUSTER-443
>             Project: mod_cluster
>          Issue Type: Bug
>          Components: Native (httpd modules)
>    Affects Versions: 1.2.9.Final, 1.3.1.Alpha2
>            Reporter: Aaron Ogburn
>            Assignee: Jean-Frederic Clere
>
> This is similar to MODCLUSTER-328, but in regards to ; instead of ?. 
> mod_cluster does not recognize ; as a delimiter when checking the request context. Thus with no trailing slash on index page requests, it treats ;jsessionid as part of the request context and tries to check the balancer for a deployed context of /helloworld;jsessionid=..., which doesn't exist and 404s. Adding the trailing slash, mod_cluster can properly delimit this and then sees the context (so /helloworld/;jsessionid=... works just fine).



--
This message was sent by Atlassian JIRA
(v6.3.8#6338)