reSIProcate

Mailing Lists

Source Code

Google Search:



< Previous by Date Date Index Next by Date >
< Previous in Thread Thread Index Next in Thread >

Re: [reSIProcate-users] Privacy header parsing

I will direct your attention to http://list.resiprocate.org/archive/resiprocate-devel/msg06465.html. I do see your point about the parameter parsing though. We probably need to define a new ParserCategory for this.

Best regards,
Byron Campen


Hi,

Has there been any work to solve the issue reported in http://list.resiprocate.org/archive/resiprocate-devel/msg06463.html?

As far as I can tell the root of the problem is that the Privacy value is of type Token, but the tokens are separated by ';' instead of ',', so only the first one is parsed as a token, and the rest as parameters. This would be possible to code around, but the 'user' parameter is defined to have a value (DataParameter), so the parser throws an exception when there is no value.
I guess I could define another value type for Privacy that doesn't attempt to parse parameters, but if the issue has already been solved I'd prefer not to. (Currently I'm running 1.3.4.)

Rgds,
Mats

_______________________________________________
resiprocate-users mailing list
resiprocate-users@xxxxxxxxxxxxxxx
List Archive: http://list.resiprocate.org/archive/resiprocate-users/

Attachment: smime.p7s
Description: S/MIME cryptographic signature