httpd-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Julian Reschke <julian.resc...@gmx.de>
Subject Re: RFC 7230..7235 Parsing Conformance?
Date Tue, 17 May 2016 18:00:42 GMT
On 2016-05-17 19:01, Graham Leggett wrote:
> On 17 May 2016, at 6:43 PM, William A Rowe Jr <wrowe@rowe-clan.net> wrote:
>
>> Wondering what other contributors are thinking on this topic.
>>
>> We have a number of changes in the ABNF grammar between
>> RFC2616 and RFC7230..7235. Do we want trunk 2.6/3.0 to be
>> an entirely RFC723x generation server, and drop all support for
>> RFC2616?
>>
>> Do we want to backport these changes to 2.4.x? If so, what
>> mechanism do we want to toggle the behavior of the server
>> between 2616 and 7230..7235?
>>
>> We can presume a small performance hit in any conditional
>> operation, especially when those decisions apply to tight parsing
>> loop. Toggling between two different parser implementations would
>> probably be a bit more efficient than conditionals within a parser
>> itself.
>
> Can you give some examples to get a sense of the extent of this?
>
> Regards,
> Graham

+1 to the question; I'd like to see examples as well...

I believe we only changed the ABNF when we came to the conclusion that 
the old one was incorrect, or did not reflect what implementations do in 
practice.

Best regards, Julian


Mime
View raw message