On Monday 10 April 2006 22:01, William A. Rowe, Jr. wrote: > 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?
Yes, it's legal. The leading slash is implied. Note: that's leading slash, which is firmly different to a trailing slash in a path. -- Nick Kew
