[SR-Users] Single-quoted vs double-quoted params in Path/Route

Iñaki Baz Castillo ibc at aliax.net
Mon Jun 4 19:29:17 CEST 2012


2012/6/4 Andreas Granig <agranig at sipwise.com>:
> Now while doing some interop tests with another platform, it turned out
> that double-quotes are not allowed in URI params (see
> https://lists.cs.columbia.edu/pipermail/sip-implementors/2008-May/019335.html,
> and in the grammar the allowed chars in the "unreserved" definition are
> "alphanum" and "mark", where "mark" is only "-" / "_" / "." / "!" / "~"
> / "*" / "'" / "(" / ")" ).
>
> Anyways, to fully comply with RFC3261, I'd like to push a bugfix to path
> module to use single-quotes instead, however it also needs a change in
> the parser to use parse_quoted_param() also in case of single-quoted
> params (which hasn't been handled at all until now).

> My question now is if there are any concerns on your side with handling
> single-quoted URI params the way we handle double-quoted ones? If we
> were strict, we'd actually need to remove the handling for double-quoted
> ones, but for backwards-compatibility I'd rather keep it there.

IMHO the more friendly solution would be parse_quoted_param() to allow
both single and double quoted values.

"Be liberal with receiving and strict while sending" :)



-- 
Iñaki Baz Castillo
<ibc at aliax.net>



More information about the sr-users mailing list