Nick Kew wrote:
On Monday 10 April 2006 20:59, [EMAIL PROTECTED] wrote:
* Prevent r->parsed_uri.path from being NULL as this can cause segmentation
faults e.g. in mod_cache. Set it to "/" in this case.
A better fix to that would surely be for apr_uri to guarantee
setting path to non-null on parsing a URI. That way it gets set
exactly when a URI is parsed.
+1. However, the exact scenario is
GET http://somehost.example.com HTTP/1.1
is this even legal? If so, what does 2616 have to say about it? If it says
to promote this to a http://somehost.example.com (based on scheme http/https)
then it doesn't hurt to do so. This gets around the issue of caching
three copies, one of http://somehost.example.com, http://somehost.example.com/
and http://somehost.example.com/index.html
Bill
