Ignore it, and then generate a proper response as if the Date header were not present in the reqeuest.
The spec advises this for proxies already, see section 16.3 which explicitly uses Date as the example: 1. Reasonable syntax check 2478 The request MUST be well-formed enough to be handled with a server transaction. Any components 2479 involved in the remainder of these Request Validation steps or the Request Forwarding section MUST 2480 be well-formed. Any other components, well-formed or not, SHOULD be ignored and remain un- 2481 changed when the message is forwarded. For instance, an element would not reject a request because 2482 of a malformed Date header field. Likewise, a proxy would not remove a malformed Date header 2483 field before forwarding a request. 2484 However, the general guidance there is good, and it follows the "be conservative with what you send, liberal in what you can receive" guideline for all IETF protocols. -Jonathan R. Neumaerker Elke wrote: > > Hi all, > > According to bis09 "the response SHOULD include a Date header field". > > How should be the reaction of a Registrar, if it detects a malformed > Date-header in the REGISTER-request ? > > (1) Ignore it and insert a correct Date-header in the REGISTER-response > ? > > (2) Ignore it and return the malformed header ? > > (3) Reject the REGISTER with 400 Bad Request ? > > > Thanks for your time, > Elke > > _____________________________________ > Email : [EMAIL PROTECTED] > > _______________________________________________ > Sip-implementors mailing list > [EMAIL PROTECTED] > http://lists.cs.columbia.edu/mailman/listinfo/sip-implementors -- Jonathan D. Rosenberg, Ph.D. 72 Eagle Rock Avenue Chief Scientist First Floor dynamicsoft East Hanover, NJ 07936 [EMAIL PROTECTED] FAX: (973) 952-5050 http://www.jdrosen.net PH: (973) 952-5000 http://www.dynamicsoft.com _______________________________________________ Sip-implementors mailing list [EMAIL PROTECTED] http://lists.cs.columbia.edu/mailman/listinfo/sip-implementors
