J. Christopher Pereira

What about a compatibiliy option that fixes 'parsed_uri.path' adding a slash at the beginning whenever the path doesn't contain a slash at the beginning?

Hi Pascal, Yes. I checked various HTTP implementations (PHP, Ruby, Java, Chrome) and all of them fix the URI path by adding a trailing slash. I only detected that Python was not fixing the path. Anyway, adding the directive will be very usfeful because generally sysadmins are not in control of what HTTP clients do, and not breaking the systems is the way to go. Thanks for your time and have a nice day.

Yes, we have a bunch of scripts which are not sending the path in the HTTP request. Besides whipping the developers of those scripts for not respecting the RFC (we will do that anyway), is there any configuration to enable support for requests without a path portion? Apache and Chrome don't complain about URL's like http://server.com?arg=1 If not, maybe mod_rewrite could be used to guarantee compatibility after enabling mod_qos on existing production systems. What would be the best solution?

Hi, Today we enabled mod_qos and detected a python script started to fail when doing HTTP requests like this: conn = httplib.HTTPConnection("my-server.com") conn.request("POST", "?a=json", params, headers) mod_qos was throwing: "access denied, invalid request line: can't parse uri" Of course, the solution was to add a trailing slash to the URI like this: ... conn.request("POST", "/?a=json", params, headers) Since Apache and browsers support requests without a trailing slash, shouldn't mod_qos support...