[reSIProcate] Qop param not double quoted

julien julien at aplix.co.jp
Thu Jul 19 22:39:04 CDT 2007


Thank you for your help!
it does look hideous at first, but after your explanation, it actually 
makes perfect sense :-)
in one case you have a list of token,
and in the other you have the choosen token.

Thank you again :-)
BR
julien


Byron Campen a écrit :
> So, qop-options does need to be quoted. However, the "qop=auth" is not 
> a qop-options, but a message-qop (see section 3.2.2), which doesn't 
> take quotes. Yes, this is hideous. A little while back, we taught the 
> parse code to accept message-qop with quotes, since so many 
> implementations end up quoting it. But we still adhere to the grammar 
> in section 3.2.2 when we emit a message-qop.
>
> Best regards,
> Byron Campen
>
>> Hello,
>> I found out after using Helper::addAuthorization(...) that the returned
>> Authorization header as some missing double quote,
>> for example qop=auth instead of qop="auth"
>>
>> in RFC 2617 we have :
>>
>> qop-options = "qop" "=" <"> 1#qop-value <">
>> qop-value = "auth" | "auth-int" | token
>>
>> so I am thinking whatever the qop-value, it MUST be quoted...
>> Could someone tell me if I am reading this correctly? ^^
>>
>> Thank you for your help
>>
>> -- 
>> Julien
>>
>> _______________________________________________
>> resiprocate-devel mailing list
>> resiprocate-devel at list.resiprocate.org
>> https://list.resiprocate.org/mailman/listinfo/resiprocate-devel
>


-- 
Julien Saito
ジュリアン 齋藤
julien at aplix.co.jp





More information about the resiprocate-devel mailing list