Thanks. That make sense.
Regards, Paul
On Mon, 28 Mar 2005 21:42:29 +0200, Jiri Kuthan jiri@iptel.org wrote:
At 06:48 AM 3/28/2005, Java Rockx wrote:
Hi All.
I'm doing some validation checks against my SIP proxy (ser-0.9.1) using SFTF http://www.sipfoundry.org/sftf/
I'm seeing that some tests are making further through my ser.cfg than I'd like.
For example, SFTF test case214 sends an INVITE message to SER with an invalid Content-Type header.
SER replies with a 404 User Not Found, which is technically correct, since the the destination doesn't exist, but SFTF complains that SER should have returned a 415 Unsupported Media Type error instead.
That's correct. SFTF aims at testing end-devices. proxy servers are not supposed to process body, 404 is correct answer in this context.
So my question is this; even though ser rejected the SIP message, shouldn't it have performed some checks on the message to validate things like Content-Type, R-URI, etc to make sure the message is not corrupt or invalid?
no. Extensibility is a feature, not a bug.
If not, does it make sense to do so before letting a SIP message get too far in to my ser.cfg?
I did find this article in the archives which seems to indicate that ser should [happliy] ignore things it doesn't understand - but is this safe?
A good proxy server should intervene with signaling as litte as it can.
-jiri