Bug 51326 - [Patch] allow session_path and session_cookie as extension attribute
Summary: [Patch] allow session_path and session_cookie as extension attribute
Status: RESOLVED FIXED
Alias: None
Product: Tomcat Connectors
Classification: Unclassified
Component: Common (show other bugs)
Version: unspecified
Hardware: All All
: P2 enhancement (vote)
Target Milestone: ---
Assignee: Tomcat Developers Mailing List
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2011-06-06 05:53 UTC by Eiji Takahashi
Modified: 2011-10-23 20:12 UTC (History)
0 users


Attachments
allow session_cookie and session_path as extension (8.00 KB, application/octet-stream)
2011-06-06 05:53 UTC, Eiji Takahashi 		Details
View All Add an attachment (proposed patch, testcase, etc.)

Note You need to log in before you can comment on or make changes to this bug.
Description Eiji Takahashi 2011-06-06 05:53:40 UTC 
Created attachment 27115 [details]
allow session_cookie and session_path as extension

session_path and session_cookie are configurable only in the load balancer section of workers.properties.

It is not convenient because the cookie name can configure per web-application on the Tomcat.

So I made the patch that allows session_path and session_cookie as extension attribute.
I tested on Linux(CentOS5.4) and WindowsXP.

Note:
The semicolon is used as separator in the rule extension syntax, but in this patch, it is not used as separator if there is a semicolon behind "session_path=".

For example, the following config is allowed:
 /sample/*=lbw;session_path=;sessionid1
In this case, ";sessionid1" is used as path parameter name.

Regards.
Comment 1 Rainer Jung 2011-10-23 20:12:51 UTC 
Thank you for your contribution.

I changed it slightly (putting the default initiaölization into common/jk_util.c) and had to adopt it to other rule extension changes I made earlier today.

It would be nice if your could test r1187963.

Will be part of 1.2.33.

Regards,

Rainer