RE: [reSIProcate] Character Escaping

["Justin Matthews" <jmatthewsr@xxxxxxxxx>]

Sorry, this is explained in RFC3261 pretty clearly (19.1.2).  # must be escaped, so resip is handling this correctly.

 

Thanks,

 

-Justin

 

---

From: resiprocate-devel-bounces@xxxxxxxxxxxxxxxxxxx [mailto:resiprocate-devel-bounces@xxxxxxxxxxxxxxxxxxx] On Behalf Of Justin Matthews
Sent: Thursday, December 08, 2005 10:30 AM
To: 'derek'; resiprocate-devel@xxxxxxxxxxxxxxxxxxx
Subject: RE: [reSIProcate] Character Escaping

 

Could someone please explain the intended way of handling special characters in resip? 

 

For example, I am trying to send an INVITE with a ‘#’ character in the To: field, ie “#15551234567@xxxxxxxxxxx”.

 

In uri.cxx, the function shoudEscapeUserChar(), determines that the ‘#’ should be escaped.  Is this correct?  The result of this is a result of “%2315551234567@xxxxxxxxxxx”.

 

Thanks,

 

-Justin

 

---

From: resiprocate-devel-bounces@xxxxxxxxxxxxxxxxxxx [mailto:resiprocate-devel-bounces@xxxxxxxxxxxxxxxxxxx] On Behalf Of derek
Sent: Thursday, February 24, 2005 8:30 PM
To: resiprocate-devel@xxxxxxxxxxxxxxxxxxx
Subject: [reSIProcate] Character Escaping

 

I merged the character escaping logic from my branch. It is controlled by HANDLE_CHARACTER_ESCAPING which is currently defined(on by default) in Uri.cxx.  We can do more work to make this even faster, but is necessary for proxies and should always be on.

 

There is a new method in Data for escaping to a stream:

 

template<class Predicate> std::ostream&

Data::escapeToStream(std::ostream& str, Predicate shouldEscape) const

 

There is also logic to handle embedded quotes in a NameAddr; this is off by default. Define HANDLE_EMBEDDED_QUOTES_DNAME in NameAddr.cxx

 

-Derek