[reSIProcate] qop Parameter Parsing
Byron Campen
bcampen at estacado.net
Mon Jan 22 11:37:52 CST 2007
Ok, the problem here is that what we expect to follow qop= is
context-sensitive; in an Authorization-type header, we expect to find
a qop-value (a non-quoted token), but in an Authenticate-type header,
we expect to see a qop-options (a quoted, comma delimited, sequence
of tokens). Unfortunately, there is currently no way to make the
parse code context-sensitive. The API for Parameter would need to
change (right now, it just looks for a quote, and if it is there, it
assumes we were looking for a qop-options). Additionally, both
Authorization-type and Authenticate-type are the same class (Auth),
so it is doubtful that this context info is even availabe in the
first place. Any opinions on how we can make this code context-
sensitive with minimal impact on the rest of the code?
Best regards,
Byron Campen
> I thought this had been fixed already at a few SIPits. I know it's
> been identified.
>
> We should accept with or without quotes.
> We must never send with quotes (in this header field - the answer's
> different for the challenge).
>
> RjS
>
> On Jan 22, 2007, at 9:18 AM, Matthias Moetje wrote:
>
>> Byron,
>>
>>
>>
>> thanks for the reply.
>>
>>
>>
>>
>>
>> The BNF in the RFC specifies that the qop in Proxy-
>> Authorization and Authorization header-field-values is unquoted.
>> People have thrown around the idea of having resip allow the
>> quoted version, but it appears that this hasn't yet been done.
>> Should we just go ahead and do this for interop's sake?
>>
>>
>>
>> I’d vote for doing so. Even if it is correct that the RFC doesn’t
>> allow quotes here, it is still wrong to classify it as qop-Options
>> in this context…
>>
>>
>>
>> I would fix it myself but I don’t have subversion installed
>> currently and I am still unsure how to determine when to parse it
>> as qop-Options and when as qop because inside this function the
>> required information (is it authentication or authorization) is
>> not available…
>>
>>
>>
>>
>>
>> Best regards,
>>
>>
>>
>> Matthias Moetje
>>
>>
>> <image001.jpg>
>> TERASENS GmbH
>> Augustenstraße 24
>> 80333 Munich
>> GERMANY
>>
>>
>>
>> Phone:
>> Fax:
>> e-mail:
>> Web:
>>
>> +49.89.143370-0
>> +49.89.143370-22
>> info at terasens.com
>> www.terasens.com
>>
>>
>>
>>
>>
>>
>>
>> <image001.jpg>
>> _______________________________________________
>> resiprocate-devel mailing list
>> resiprocate-devel at list.resiprocate.org
>> https://list.resiprocate.org/mailman/listinfo/resiprocate-devel
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://list.resiprocate.org/pipermail/resiprocate-devel/attachments/20070122/99c76876/attachment.htm>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: smime.p7s
Type: application/pkcs7-signature
Size: 2423 bytes
Desc: not available
URL: <http://list.resiprocate.org/pipermail/resiprocate-devel/attachments/20070122/99c76876/attachment.bin>
More information about the resiprocate-devel
mailing list