Although it seems we will be going to BNF as a regex someday, I am
suspicious that this very issue is causing incompatibility with a HTTP
1.1 server I am trying to access. So I may make a stab at parsing this
chunk size thing as I wrote below. Am I right in assuming this patch
should go to bug 12607?
--
Ryan Hoegg
ISIS Networks
Ortwin Glück wrote:
> LWS = [CRLF] 1*( SP | HT )
>
> Damn. We must parse this shit....
>
> Ryan Hoegg wrote:
>
>> I have never seen a server do this, but you are right about the
>> quoted-string:
>>
>> quoted-string = ( <"> *(qdtext | quoted-pair ) <"> )
>> quoted-pair = "\" CHAR
>> qdtext = <any TEXT except <">>
>>
>> TEXT = <any OCTET except CTLs,
>> but including LWS>
>>
>> So it seems that for each cunk-ext-val, we need to:
>> 1) read the first char
>> 2) if it is not a <">, proceed as we currently do
>> 3) if it is, continue to read chars until a <"> or a <\> is reached
>> 4) in the case of a <\>, skip the next character
>> 5) in the case of a <">, ensure that we either have CRLF or <;>
>> 6) if we have <;>, we read another <token=token|quoted-string> i.e.
>> goto 1
>>
>> This is my reading of RFC2616.
>
--
To unsubscribe, e-mail: <mailto:commons-dev-unsubscribe@jakarta.apache.org>
For additional commands, e-mail: <mailto:commons-dev-help@jakarta.apache.org>
|