Bill Barker wrote:
But since the request is supposed to be atomic why to strdup an uri?
I'd rather remove
char *uri = apr_pstrdup(r->pool, r->uri);
before calling map_uri_to_worker then adding strdup to IIS.
It was done to fix a '//' bypass traversal bug (e.g.
http://myserver/myapp//foo.jsp would serve the source of the JSP).
Yep, but is that really the responsibility of the JK?
The jk is supposed to be a proxy, so as less intervention in the
protocol the better results will be.
I have comment out the jk_no2slash checking inside map_uri_to_worker
cause found no difference with or without it.
Regards,
Mladen.
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
