On Aug 19, 2008, at 11:44 PM, William A. Rowe, Jr. wrote:
William A. Rowe, Jr. wrote:
Different issue; different response.
Bill Barker wrote:
Nick Kew [EMAIL PROTECTED] wrote in message
-1. Semicolon is a perfectly valid character in a session-id, so
that
risks breaking other apps. The
On 21 Aug 2008, at 13:39, Jim Jagielski wrote:
In any case, I agree that both solutions are non-optimal... This
leads me to believe that whether we should treat ';' as special
for session/route data should be runtime configurable. I propose
a simple envar... Sound OK?
+1.
(assuming I
[EMAIL PROTECTED] wrote:
-path = apr_strtok(apr_pstrdup(pool, path), ?, q);
+path = apr_strtok(apr_pstrdup(pool, path), ;?, q);
-1. Semicolon is a perfectly valid character in a session-id, so that
risks breaking other apps. The fact that Tomcat treats it as
Nick Kew [EMAIL PROTECTED] wrote in message
news:[EMAIL PROTECTED]
[EMAIL PROTECTED] wrote:
-path = apr_strtok(apr_pstrdup(pool, path), ?, q);
+path = apr_strtok(apr_pstrdup(pool, path), ;?, q);
-1. Semicolon is a perfectly valid character in a session-id,
Different issue; different response.
Bill Barker wrote:
Nick Kew [EMAIL PROTECTED] wrote in message
-1. Semicolon is a perfectly valid character in a session-id, so that
risks breaking other apps. The fact that Tomcat treats it as a
separator doesn't commit other appservers to do the same.
William A. Rowe, Jr. wrote:
Different issue; different response.
Bill Barker wrote:
Nick Kew [EMAIL PROTECTED] wrote in message
-1. Semicolon is a perfectly valid character in a session-id, so that
risks breaking other apps. The fact that Tomcat treats it as a
separator doesn't commit other
