Hello, We are having some difficulty with encoded slashes being decoded in our URLs. According to the version.signature file we are using IBM HTTP Server 6.0.2.1.
We have set the 'AllowEncodedSlashes' directive to 'On' which gets us past
a 404 error, but the encoded slashes are decoded by the time they get to
our application running on WebSphere Application Server 6.0.2.19 with http
plugin 6.0.0.0.
For example:
/wfsp/wfsp/registry/pullProject/%2Flwpcn06+SSL+test4
shows up as
/wfsp/wfsp/registry/pullProject//lwpcn06+SSL+test4
I have seen related postings and bug reports in regards to 'proxy'
functionality, however from looking at our httpd.conf all proxy content is
commented out.
Any ideas would be greatly appreciated.
Cheers,
Rob
httpd.conf
Description: Binary data
--------------------------------------------------------------------- The official User-To-User support forum of the Apache HTTP Server Project. See <URL:http://httpd.apache.org/userslist.html> for more info. To unsubscribe, e-mail: [EMAIL PROTECTED] " from the digest: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
