[reSIProcate] NameAddr::parse() bug?

Scott Godin slgodin at icescape.com
Tue Nov 8 10:38:53 CST 2005


I don't mind making this change to resip, if everyone agrees.  : )

Should we allow spaces in the unquoted display name - or just stop
parsing at either LWS or < - as the RFC suggests?

Scott Godin

> -----Original Message-----
> From: Francesco Fondelli [mailto:francesco.fondelli at gmail.com]
> Sent: Tuesday, November 08, 2005 11:27 AM
> To: Scott Godin
> Cc: resiprocate-devel at list.sipfoundry.org
> Subject: Re: [reSIProcate] NameAddr::parse() bug?
> 
> Scott Godin wrote:
> 
> > The following NameAddr will produce a trailing space in the display
> > name:
> > DisplayName <sip:user at host.com>
> >
> > In this case display name is "DisplayName " - is that correct?   Or
> > should it be "DisplayName"?
> 
> hemm I meant exactly the same thing in my prev example:
> 
> From: 0015556678 <sip:foo at 192.168.6.177>;tag=as548e6f07
> 
> and as Scott Lawrence said and IMHO resip should behave like
sipXtackLib.
> 
> It might not be considered a bug but I'm going to strip that space
> out in my production environment.
> 
> Regards
> FF



More information about the resiprocate-devel mailing list