Thanks for the replies. I have made changes to pass those input challenge values without quotes.
Sandip -----Original Message----- From: Chris Boulton [mailto:[EMAIL PROTECTED] Sent: Tuesday, September 16, 2003 03:13 PM To: Attila Sipos; sandip; [EMAIL PROTECTED] Subject: RE: [Sip-implementors] WWW-Authenticate decoding problem That is right - only use quotes when explicitly told to do so:- e.g. "qop" "=" <"> 1#qop-value <"> Chris. >-----Original Message----- >From: Attila Sipos [mailto:[EMAIL PROTECTED] >Sent: 16 September 2003 10:39 >To: 'sandip'; [EMAIL PROTECTED] >Subject: RE: [Sip-implementors] WWW-Authenticate decoding problem > > >Hi Sandip, > >If it has quotes in the grammar, it means use it >without quotes in the actual header. > >> algorithm = "algorithm" EQUAL ( "MD5" / "MD5-sess" >> / token ) > >So > algorithm=MD5 >or > algorithm=MD5-sess >are both OK. > > >Note: if you use your rule for quotes then you >would get something like: > "algorithm"="MD5" >which is clearly not right. > >Regards, > >Attila > > >> -----Original Message----- >> From: sandip [mailto:[EMAIL PROTECTED] >> Sent: 16 September 2003 10:26 >> To: [EMAIL PROTECTED] >> Subject: [Sip-implementors] WWW-Authenticate decoding problem >> >> >> Hi All, >> Got a problem with the decoding of WWW-Authenticate header. >> >> I think, for WWW-Authenticate header the grammer ( ABNF ) has >> contradiction >> with the example shown in RFC 3261 for the following parameters. >> 1. stale >> 2. algorithm >> >> For both of these challenge parameters, ABNF(page 231,section >> 25.1, RFC >> 3261) dictates the values for these are to be given as a double-quoted >> string. But the examples given in the RFC does not have a >> double-quoted >> value for those. So I am at confusion. This makes disorder >> resulting from a >> failure to behave predictably the header decoding. >> >> Please suggest me what to accept. >> >> TIA, >> Sandip >> >> >> >> >> Examples Given in RFC (3261) : >> >> WWW-Authenticate: Digest realm="atlanta.com", >> domain="sip:boxesbybob.com", qop="auth", >> nonce="f84f1cec41e6cbe5aea9c8e88d359", >> opaque="", stale=FALSE, algorithm=MD5 >> >> >> >> >> >> BNF says the grammar for the header as : >> >> WWW-Authenticate = "WWW-Authenticate" HCOLON challenge >> >> challenge = ("Digest" LWS digest-cln *(COMMA digest-cln)) >> / other-challenge >> other-challenge = auth-scheme LWS auth-param >> *(COMMA auth-param) >> digest-cln = realm / domain / nonce >> / opaque / stale / algorithm >> / qop-options / auth-param >> realm = "realm" EQUAL realm-value >> realm-value = quoted-string >> domain = "domain" EQUAL LDQUOT URI >> *( 1*SP URI ) RDQUOT >> URI = absoluteURI / abs-path >> nonce = "nonce" EQUAL nonce-value >> nonce-value = quoted-string >> opaque = "opaque" EQUAL quoted-string >> stale = "stale" EQUAL ( "true" / "false" ) >> algorithm = "algorithm" EQUAL ( "MD5" / "MD5-sess" >> / token ) >> >> >> _______________________________________________ >> Sip-implementors mailing list >> [EMAIL PROTECTED] >> http://lists.cs.columbia.edu/mailman/listinfo/sip-implementors >> >_______________________________________________ >Sip-implementors mailing list >[EMAIL PROTECTED] >http://lists.cs.columbia.edu/mailman/listinfo/sip-implementors
<<attachment: winmail.dat>>
_______________________________________________ Sip-implementors mailing list [EMAIL PROTECTED] http://lists.cs.columbia.edu/mailman/listinfo/sip-implementors
