Topic: Apache 2.2.22 and random 400's with %2F

[vtjay79]

Hello,

I have an application that builds paths to JS files in URL's and encodes the slashes with '%2F'.

I can't seem to make sense of it, but eventualy after several hours, or several days, or even several weeks it will start producing 400's in the access log for anything with a %2F in it.

I tried googling which had me put in the AllowEncodedSlashes directive in my main conf as well as any vhosts.

I tried 'On' and 'NoDecode', but the same thing happens after a few days time.

I set the log level to "info" and scoured it looking for anything in between the prior 200 time with a %2F in the URL and the 400 without anything of interest.

I have another server thats awaiting an approval to use with 2.2.27 on it that doesn't seem to have any of these 400's in it, but, it also doesn't have but 1 user ever other few days.

The fix seems simple, a start and stop of the service, but, I have users all around the world and it would be nice if it just worked.

Any ideas would be greatly appreciated.

[James Blond]

See http://httpd.apache.org/docs/current/mod/core.html#allowencodedslashes