Closed bboyle closed 10 years ago
Entering a slash in the template form encodes the slash as %2F This causes a file not found error on arewemeetingyet.com
%2F
Example: http://arewemeetingyet.com/Brisbane/2014-03-16/22:00/foo%2Fbar
Huh, that's really weird. It almost seems like an Apache bug...
This works now, using by setting AllowEncodedSlashes to NoDecode in the Apache config.
AllowEncodedSlashes
NoDecode
(See also 6465b953.)
Entering a slash in the template form encodes the slash as
%2F
This causes a file not found error on arewemeetingyet.comExample: http://arewemeetingyet.com/Brisbane/2014-03-16/22:00/foo%2Fbar