reSIProcate

Mailing Lists

Source Code

Google Search:



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

Re: [repro-users] URI scheme check isssue in Repro

Technically speaking, it is a bug. Not a particularly harmful bug, sure, but still a bug. More importantly, the code is doing something unexpected here, and that is always worth investigating.
So, perhaps what is happening is that these are parsing (since our parser doesn't do deep validation; sip:::::alice@xxxxxxx may be parsing as scheme="sip", user="::::alice", domain"abc.com", and sip:alice@@@@abc.com may be parsing as scheme="sip", user="alice", domain="@@@abc.com"), and something later on is getting upset. Do you have any logs of this? 

Best regards,
Byron Campen



While a 500 response to this problem is not strictly correct it should
not cause any interoperability issues with the UAC. In other words, I
don't think this is really a bug.

Jason
On Tue, May 6, 2008 at 6:52 AM, Byron Campen <bcampen@xxxxxxxxxxxx> wrote: 

 Constraining the discussion to repro-users.
The first and last should yield a 416, the other two are malformed and I 
would expect a 400 to come back. What revision are you using?

Best regards,
Byron Campen






Hi,
I am trying some scenarios in Repro where in I send Invite messages with 
improper Request URI formats, for ex: "sippppp:alice@xxxxxxx" or
"sip:::::alice@xxxxxxx" or "sip:alice@@@@abc.com" or "XYZ:alice@xxxxxxx". The expected behavior is to get a 416 Unsupported URI scheme, but I get 500 
Internal server error.





Why does it happen so, is it a bug?????



Thanks and Regards,

-Sandeep A
_______________________________________________
repro-users mailing list
repro-users@xxxxxxxxxxxxxxx
https://list.resiprocate.org/mailman/listinfo/repro-users

_______________________________________________
 repro-users mailing list
 repro-users@xxxxxxxxxxxxxxx
 https://list.resiprocate.org/mailman/listinfo/repro-users

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