http - 'Most conservative' conversion to GMT? -


HTTP 1.1 RFC (2616) Section 1 9.3 "tolerant application calls concerning the dates parsing of" HTTP client applications:

If an HTTP header takes a wrong date with a time zone other than GMT, then it should be converted to GMT using the most conservative possible conversion.

Two questions:

  1. Does this mean that the server should change the non-GMT date value for GMT? Or does it mean that if it (optionally) chooses to convert the non-GMT date value to GMT (instead of denying it), should it be the most conservative possible conversion?

Edit However, now it is an old question, I am still interested if any, on getting the answer

Does this mean that the server values ​​a GMT date for a non GMT? Or does this mean that if (optionally) it chooses to change the non-GMT date value to GMT (instead of denying it), then should it use the most conservative possible conversion?

This is actually something that is specific in the field of question, which usually applies. There is no one to say about the conversion in the cache:

  • The HTTP / 1.1 client and the cache should agree that an RFC-850 date appears to be in the future for more than 50 years Fact in the past (help to solve this problem "year 2000" Does).
  • Although all date formats are specified to be case-sensitive, recipients should see the case of day, week and timezone names as insensitive.
  • An HTTP / 1.1 implementation can internally represent the period of expiry before the fair value, but the end date of a parse is not internally represented later than the fair value should do.
  • All termination-related calculations should be done in GMT. The local time zone will not affect the calculation or comparison of an age or end time.
  • Cache should consider dates with other time zones other than "GMT".

What does "the most conservative potential conversion" mean?

Under this context, being faced with 2 results does not seem particularly special on one side, based on the date reference, the date of "conservative".

In the context of a finally modified header, the most conservative will be "later" in terms of a but one ending header, 2 Before are more conservative Any significant amount of guessing should only return an error response.


Comments

Popular posts from this blog

java - NullPointerException for a 2d Array -

python - Assemble mpeg file unable to play in mediaplayer -

c# - NameSpace Manager or XsltContent to parse aspx page -