Re: [reSIProcate] Privacy header parsing
Yuck. We will need to come up with a new ParserCategory (or even LazyParser, since Privacy header-field-values don't have params) for this express purpose. I'll put this in bugzilla.
Best regards, Byron Campen
All, I think the 'Privacy' header is parsed incorrectly. We had some problems with the following header:- "Privacy: user;id" When I try to extract to individual tokens I get a c++ exception. It looks like resip expects the values to be comma delimited, however the specification (RFC 3323) has semi colon delimiters. Rob. ============================ Robert Mansfield Senior Software Engineer Redwood Technologies Limited The Redwood Building, Broad Lane, Bracknell, Berkshire, RG12 9GU, U.K. Registered in England No. 2817863 T +[44] (0)1344 304 344 F +[44] (0)1344 304 345 E rjm@xxxxxxxxxxxxxxx W www.redwoodtech.com ===== Email Disclaimer The information in this email is confidential and may be legally privileged. It is intended solely for the addressee. Access to this email by anyone else is unauthorised. If you are not the intended recipient, any disclosure, copying, distribution or any action taken or omitted to be taken in reliance on it is prohibited and may be unlawful. When addressed to our clients any opinions or advice contained in this email are subject to the limitations of Redwood Technologies Limited's standard terms and conditions of contract. _______________________________________________ resiprocate-devel mailing list
|
Attachment:
smime.p7s
Description: S/MIME cryptographic signature