On Tue, Sep 13, 2016 at 10:10 AM, Ruediger Pluem <[email protected]> wrote:
>
>
> On 09/13/2016 04:19 AM, Eric Covener wrote:
>> On Mon, Sep 12, 2016 at 5:38 PM, William A Rowe Jr <[email protected]>
>> wrote:
>>> It really seems that if a major client is not handling "|" correctly, we
>>> need to carve out an exception,
>>
>> +1 to allow it.
>>
>> For others who might hit a maze of closed/duped bug reports this one
>> is active this year:
>> https://bugzilla.mozilla.org/show_bug.cgi?id=1064700
>>
>
> +1
+1, but I wouldn't put the exception in T_URI_RFC3986 (rather where it is used).
We could still do things like:
ll = uri;
/* firefox bug exception w.r.t pipe */
while ((ll = ap_scan_http_uri_safe(ll)) && *ll == '|')
ll++;
Less simple, but it looks more correct to me, once firefox fixes its
bug we don't change T_URI_RFC3986's (expected) behaviour.
Regards,
Yann.
