Look at the following example of Authorization header and its params.
Authorization = "Authorization" HCOLON credentials
credentials = ("Digest" LWS digest-response)
/ other-response
digest-response = dig-resp *(COMMA dig-resp)
dig-resp = username / realm / nonce / digest-uri
/ dresponse / algorithm / cnonce
/ opaque / message-qop
/ nonce-count / auth-param
username = "username" EQUAL username-value
username-value = quoted-string
digest-uri = "uri" EQUAL LDQUOT digest-uri-value RDQUOT
digest-uri-value = rquest-uri ; Equal to request-uri as specified
by HTTP/1.1
message-qop = "qop" EQUAL qop-value
cnonce = "cnonce" EQUAL cnonce-value
cnonce-value = nonce-value
nonce-count = "nc" EQUAL nc-value
nc-value = 8LHEX
dresponse = "response" EQUAL request-digest
request-digest = LDQUOT 32LHEX RDQUOT
auth-param = auth-param-name EQUAL
( token / quoted-string )
auth-param-name = token
other-response = auth-scheme LWS auth-param
*(COMMA auth-param)
auth-scheme = token
Please look at the auth-param it can be auth-param-name which in turn
may be token (non-quoted) or quoted string.
So, it really depends on the implementation of the softwares. But some
params mandate quotes for example look at
username-value for username param.
So, you would catch parser error for the message which is against ABNF
of RFC 3261 but really depends on implementation.
Some implementations may have relaxed rules for better interoperability
and some don't. So, you may end-up having some gateways
understanding both quoted and non-quoted params.
Somesh
* Please donot take the print out of this e-mail unless its absolutely
necessary *
________________________________
From: friend friend [mailto:[email protected]]
Sent: Tuesday, January 27, 2009 4:29 PM
To: [email protected]; Somesh S. Shanbhag
Subject: RE: [Sip-implementors] Regarding Authorization Header Parameter
Could you please tell me, all the Tokens must not have double quotes and
All the quoted strings must have double quotes?
If RFC doesn't mandate, why some of Gateway not responding for without
double quotes?
-Kannan
--- On Tue, 27/1/09, Somesh S. Shanbhag <[email protected]> wrote:
From: Somesh S. Shanbhag <[email protected]>
Subject: RE: [Sip-implementors] Regarding Authorization Header
Parameter
To: [email protected],
[email protected]
Date: Tuesday, 27 January, 2009, 3:08 PM
Strictly speaking according to grammer, most of the known
parameters of
WWW-Authenticate and Authorization are quoted strings. But RFC
doesn't
mandate it should be a quoted string.
For example:
nonce-count = "nc" EQUAL nc-value
nc-value = 8LHEX
nonce-count is a number and not in quotes according to ABNF
-Somesh
* Please donot take the print out of this e-mail unless its
absolutely
necessary *
-----Original Message-----
From: [email protected]
[mailto:[email protected]] On
Behalf Of friend
friend
Sent: Tuesday, January 27, 2009 2:58 PM
To: [email protected]
Subject: [Sip-implementors] Regarding Authorization Header
Parameter
Hi folks,
I have a doubt in Authorization & WWW-Authenticate Headers
Parameters...
All the parameters must have double quotes in both headers.
If not sending with double quotes, some of softphone or
Gateway(ITSP)
accepting but some of softphone or Gateway not accepting.
Could you please clarify what are all the parameters must have
double quotes?
Thanks n Advance
Thanks & Regards,
Kannan
Check out the all-new face of Yahoo! India. Go to
http://in.yahoo.com/
_______________________________________________
Sip-implementors mailing list
[email protected]
https://lists.cs.columbia.edu/cucslists/listinfo/sip-implementors
EMAIL DISCLAIMER : This email and any files transmitted with it
are
confidential and intended solely for the use of the individual
or entity to whom
they are addressed. Any unauthorised distribution or copying is
strictly
prohibited. If you receive this transmission in error, please
notify the sender
by reply email and then destroy the message. Opinions,
conclusions and other
information in this message that do not relate to official
business of Mascon
shall be understood to be neither given nor endorsed by Mascon.
Any information
contained in this email, when addressed to Mascon clients is
subject to the
terms and conditions in governing client contract.
Whilst Mascon takes steps to prevent the transmission of viruses
via e-mail, we
can not guarantee that any email or attachment is free from
computer viruses and
you are strongly advised to undertake your own anti-virus
precautions. Mascon
grants no warranties regarding performance, use or quality of
any e-mail or
attachment and undertakes no liability for loss or damage,
howsoever caused.
________________________________
Add more friends to your messenger and enjoy! Invite them now.
<http://in.rd.yahoo.com/tagline_messenger_6/*http:/messenger.yahoo.com/i
nvite/>
EMAIL DISCLAIMER : This email and any files transmitted with it are
confidential and intended solely for the use of the individual or entity to
whom they are addressed. Any unauthorised distribution or copying is strictly
prohibited. If you receive this transmission in error, please notify the sender
by reply email and then destroy the message. Opinions, conclusions and other
information in this message that do not relate to official business of Mascon
shall be understood to be neither given nor endorsed by Mascon. Any information
contained in this email, when addressed to Mascon clients is subject to the
terms and conditions in governing client contract.
Whilst Mascon takes steps to prevent the transmission of viruses via e-mail, we
can not guarantee that any email or attachment is free from computer viruses
and you are strongly advised to undertake your own anti-virus precautions.
Mascon grants no warranties regarding performance, use or quality of any e-mail
or attachment and undertakes no liability for loss or damage, howsoever caused.
_______________________________________________
Sip-implementors mailing list
[email protected]
https://lists.cs.columbia.edu/cucslists/listinfo/sip-implementors
