[SR-Users] uri parameter value case sensitiveness

Juha Heinanen jh at tutpro.com
Fri May 16 19:56:54 CEST 2014

Daniel-Constantin Mierla writes:

> For a specific example, is it allowed that the value of a parameter in 
> contact header uri is changed to upper/lower case when building the 
> sequential request (so this appears in request uri)? Same would be for 
> Recor-Route uri parameter that would appear later in Route headers...

i found this from rfc3261:

19.1.4 URI Comparison
• Comparison of the userinfo of SIP and SIPS URIs is
case-sensitive. This includes userinfo containing passwords or formatted
as telephone-subscribers. Comparison of all other components of the URI
is case-insensitive unless explicitly defined otherwise.


7.3.1 Header Field Format
When comparing header fields, field names are always
case-insensitive. Unless otherwise stated in the defi- nition of a
particular header field, field values, parameter names, and parameter
values are case-insensitive.  Tokens are always case-insensitive. Unless
specified otherwise, values expressed as quoted strings are case-

and example:

Content-Disposition: session;handling=optional

is equivalent to

content-disposition: Session;HANDLING=OPTIONAL

-- juha

More information about the sr-users mailing list