I thought that all literal values (enclosed in
quotes in the ABNF) were case-sensitive.

Looking at RFC2822 I was wrong...

   Characters will be specified either by a decimal value
   (e.g., the value %d65 for uppercase A and %d97 for lowercase A) or by
   a case-insensitive literal value enclosed in quotation marks (e.g.,
   "A" for either uppercase or lowercase A).  


My apologies.

Attila


>> -----Original Message-----
>> From: Paul Kyzivat [mailto:[EMAIL PROTECTED]
>> Sent: 23 November 2005 16:57
>> To: Attila Sipos
>> Cc: Christian Jansson; [email protected]
>> Subject: Re: [Sip-implementors] Is it ok to rearrange 
>> (compact form/WS)
>> Fromheader?
>> 
>> 
>> 
>> 
>> Attila Sipos wrote:
>> > Hi Christian,
>> > 
>> > I don't know where the RFC mentions
>> > this so I give my answers intuitively...
>> > 
>> > I think the first 2 examples would be OK but
>> > the 3rd is not because "FROM" is not a legal
>> > SIP header.
>> 
>> Why do you say that? Header names are case-insensitive.
>> 
>>      Paul
>> 
>> > You might also (though you shouldn't) get
>> > problem with primitive parsers which do a
>> > string compare along the length of the whole line.
>> > 
>> > Best Regards,
>> > 
>> > Attila
>> > 
>> > Attila Sipos
>> > http://www.vegastream.com
>> > 
>> > 
>> > 
>> > 
>> >>>-----Original Message-----
>> >>>From: [EMAIL PROTECTED]
>> >>>[mailto:[EMAIL PROTECTED] Behalf 
>> >>>Of Christian
>> >>>Jansson
>> >>>Sent: 23 November 2005 14:54
>> >>>To: [email protected]
>> >>>Subject: [Sip-implementors] Is it ok to rearrange 
>> (compact form/WS)
>> >>>Fromheader?
>> >>>
>> >>>
>> >>>
>> >>>Is it ok to change the way a From (To, etc) header looks, 
>> >>>either when a
>> >>>request is being proxied, or when the UAS creates a response? For
>> >>>example to switch between compact and non compact form, 
>> and to add or
>> >>>remove optional spaces.
>> >>>
>> >>>3 examples:
>> >>>
>> >>>"From: a"        -> "f: a"
>> >>>"f: a"           -> "From: a"
>> >>>"From :a ;param" -> "FROM: a;param"
>> >>>
>> >>>Pointers into RFC 3261 that allows/disallows this would be 
>> >>>very helpful.
>> >>>
>> >>>/ Christian Jansson
>> >>>
>> >>>
>> >>>_______________________________________________
>> >>>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
>> > 
>> 

_______________________________________________
Sip-implementors mailing list
[email protected]
http://lists.cs.columbia.edu/mailman/listinfo/sip-implementors

Reply via email to