[reSIProcate] [Bug 11] Privacy headers are parsed incorrectly.
https://www.resiprocate.org/bugzilla/show_bug.cgi?id=11
Alan Hawrylyshen <alan@xxxxxxxxxxxx> changed:
What |Removed |Added
----------------------------------------------------------------------------
CC| |alan@xxxxxxxxxxxx
--- Comment #1 from Alan Hawrylyshen <alan@xxxxxxxxxxxx> 2008-11-26 10:59:16
---
That's a nasty spec flaw. How did that get past the ABNF review? :-)
It would be possible to enter a 'privacy' pre-parse / mhs state. We could
easily 'act like a multi header' when dealing with privacy. The MHS knows this
and it would only be a few states (with some cleverness, it wouldn't even
affect the complexity of the FSM all that much).
Which is it? The fix might be cleaner at the MHS phase, but that would have
impacts on the encoding side. I mean is it REALLY a multi-header with a
different separator. If anything else is different then it will fail epically
to try to make the changes at the MHS/encoder levels.
Some implementer should have complained LOUDLY about this prior to getting to
RFC status.
--
Configure bugmail: https://www.resiprocate.org/bugzilla/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the assignee for the bug.