Re: [reSIProcate] qop Parameter Parsing

["Matthias Moetje" <moetje@xxxxxxxxxxxx>]

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

TERASENS GmbH
Augustenstraße 24
80333 Munich
GERMANY

 

Phone: Fax: e-mail: Web:

+49.89.143370-0 +49.89.143370-22 info@xxxxxxxxxxxx www.terasens.com