emptySessionPath with HTTP/1.1 Connector

[joe563za2]

Using emptySessionPath="true" with HTTP/1.1 Connector does not seem to work with JBoss 5.0.0.GA anymore as I still get my JSESSIONID cookie set with Path=/[contextRoot] instead of just Path=/ .

I need this behaviour as I have a load balancer (non-apache hence I can't use mod_jk) in front of my application and I do url rewriting to route the requests to the correct application. Has this attribute been removed from JBoss 5.0.0.GA - I noticed that the parameter is not set by default as it was with 4.0.2.

Anyone else experienced the same?

[c.h.]

same problem.
in jboss4 works, in jboss5 doesn't

[webalgorithm]

Yep, same issue here. I am in the processing of upgrading from 4.0.5 GA to 5.1.0 GA. In my case in manifests itself even without load balancing. I am using mod_jk with rewrites.

My app is deployed as "web.war" (exploded - not sure if that makes any difference), <context-root>web</context-root>.

Requests such as http://hostname/web/myaccount.htm are 100% ok.

Requests such as http://hostname/web/myaccount.htm result in new sessionid 100% of the time.

Clearly an issue with cookie path.

Also interesting: I tested this with all 4.x versions of JBoss - no issues. All 5.x versions exhibit this behavior.

Any suggestions? I've tried playing around with emptySessionPath - does not seem to have much impact.

[webalgorithm]

"webalgorithm" wrote:


Sorry, please read this post instead of my prior one.

Yep, same issue here. I am in the processing of upgrading from 4.0.5 GA to 5.1.0 GA. In my case in manifests itself even without load balancing. I am using mod_jk with rewrites.

My app is deployed as "web.war" (exploded - not sure if that makes any difference), <context-root>web</context-root>.

Requests such as http://hostname/web/myaccount.htm are 100% ok.

Requests such as http://hostname/myaccount.htm result in new sessionid 100% of the time. (note that apache rewrites this url RewriteRule ^(\w+).htm(\w+)?$ web/$1.htm$2 [L])

Clearly an issue with cookie path.

Also interesting: I tested this with all 4.x versions of JBoss - no issues. All 5.x versions exhibit this behavior.

Any suggestions? I've tried playing around with emptySessionPath - does not seem to have much impact.

[jfclere]

See http://www.jboss.org/index.html?module=bb&op=viewtopic&p=4237596#4237596

[joe563za2]

Thanks