On Mon, 10 Apr 2006 23:50:05 +0200
Ruediger Pluem <rpluem@apache.org> wrote:
>
>
> On 04/10/2006 11:19 PM, Davi Arnaut wrote:
> > On Mon, 10 Apr 2006 16:01:29 -0500
> > "William A. Rowe, Jr." <wrowe@rowe-clan.net> wrote:
> >
> >
> >>Nick Kew wrote:
> >>
> >>>On Monday 10 April 2006 20:59, rpluem@apache.org 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
>
> I also thought initially to fix this in apr-util, but right know I am not
> sure about it, because IMHO apr_uri_parse should do generic uri parsing.
> Setting an empty uri to "/" seems to be HTTP specific, so I am not sure
> if we should do this in apr_uri_parse. At least we would need to check
> whether the scheme is http or https.
>
> Regards
>
> Rüdiger
>
>
After reading RFC 2396 (Uniform Resource Identifiers), well I think it's
scheme dependent (<scheme-specific-part>), but I'm not 100% sure:
3. URI Syntactic Components
The URI syntax is dependent upon the scheme. In general, absolute
URI are written as follows:
<scheme>:<scheme-specific-part>
An absolute URI contains the name of the scheme being used (<scheme>)
followed by a colon (":") and then a string (the <scheme-specific-
part>) whose interpretation depends on the scheme.
...
<scheme>://<authority><path>?<query>
each of which, except <scheme>, may be absent from a particular URI.
For example, some URI schemes do not allow an <authority> component,
and others do not use a <query> component.
...
--
Davi Arnaut
|