On 06/03/14 03:40, Juha Heinanen wrote:
Daniel-Constantin Mierla writes:
core/parser: handle the case when username field
in auth header has
proto scheme
- some phones put there "sip:username@domain", so far it was handling
"username" and "username@domain"
is this a bug fix, i.e.,
can username according to the relevant rfcs
have uri scheme?
Some devices uses user@domain for username part of the
authorization
header, which I guess is not allowed as well. But we support it for long
time, the reason of having ha1 and ha1b in subscriber table. Now I
discovered that some snom puts even sip: in front of usern@domain when
doing xcap operations. So it is just a safety check, skipping the scheme
if it is, otherwise authentication fails. The parser in that part is not
a full uri parser, it uses char find.
Daniel
--
Daniel-Constantin Mierla -
http://www.asipto.com
http://twitter.com/#!/miconda -
http://www.linkedin.com/in/miconda