[EMAIL PROTECTED] == [EMAIL PROTECTED]
We store the endpoints always as lowercase. When doing lookups we lowercase the input and search for a match. As a practical matter are SIP endpoints with case-sensitive userinfo's used? For example, someone setting up bob and Bob as 2 different accounts under the same host. If that is the case then we need to rethink our database schema to preserve the case of the userinfo when doing lookups for SIP endpoints.
Tory
Tory Patnoe wrote:
I noticed that the SIP URL userinfo portion changed from being case-insensitive in RFC-2543 to case-sensitive comparison in RFC-3261.
RFC-2543 section 2
SIP URLs are case-insensitive, so that for example the two URLs
sip:[EMAIL PROTECTED] <mailto:[EMAIL PROTECTED]> and SIP:[EMAIL PROTECTED] <mailto:[EMAIL PROTECTED]> are equivalent. All
URL parameters are included when comparing SIP URLs for equality.
RFC-3261 Section 19.1.4
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.
<snip>
The URIs within each of the following sets are not equivalent:
SIP:[EMAIL PROTECTED] <mailto:[EMAIL PROTECTED]>;Transport=udp (different usernames)
sip:[EMAIL PROTECTED] <mailto:[EMAIL PROTECTED]>;Transport=UDP
I searched for a reason for the change but couldn't find one. Can someone explain? Obviously I'm running into problems.
Tory Patnoe
_______________________________________________ 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
