"Andrea Rizzi" <[EMAIL PROTECTED]> asks: > RFC3261 seems to me to not address the UAC behavior when receiving a non-100 > provisional response containing a malformed header. > > > > Has anybody any suggestion about?
I would suggest doing what the torture test RFC (RFC 4475) says. Basically, in several examples there are messages that have malformed headers but you can figure out what the sender meant (say, 'From: Bell, Alexander <sip:[EMAIL PROTECTED]>;tag=43', like in section 3.1.2.15) then you should be liberal in what you accept. In particular, RFC 4475 says (in section 3.1.2.15) regarding the example From header An element may attempt to be liberal in what it receives and infer the missing quotes. If this element were a proxy, it must not propagate the error into the request it forwards. As a consequence, if the fields are covered by a signature, there's not much point in trying to be liberal - the message should simply be rejected. In any event, if a response is hopelessly mangled, there's nothing you can really do except drop the response and clean up (say, by informing the user that the call failed). frank _______________________________________________ Sip-implementors mailing list Sip-implementors@cs.columbia.edu https://lists.cs.columbia.edu/cucslists/listinfo/sip-implementors
