#756 ✓resolved
7uc0

HTTP/1.1 compliance Date

Reported by 7uc0 | April 20th, 2011 @ 08:04 PM | in 1.3 (closed)

Switching from 1.0.3.2 to 1.1.1, I noticed Date Field is not present
in header anymore, RFC mentions it should be present by default,
except for server side error / non accurate support.

http://tools.ietf.org/html/rfc2616#section-14.18

14.18 Date
The Date general-header field represents the date and time at which the message was originated, having the same semantics as orig-date in
RFC 822. The field value is an HTTP-date, as described in section 3.3.1; it MUST be sent in RFC 1123 [8]-date format.

   Date  = "Date" ":" HTTP-date

An example is

   Date: Tue, 15 Nov 1994 08:12:31 GMT

Origin servers MUST include a Date header field in all responses, except in these cases:

  1. If the response status code is 100 (Continue) or 101

(Switching

     Protocols), the response MAY include a Date header field, at 
     the server's option. 
  2. If the response status code conveys a server error, e.g. 500 
     (Internal Server Error) or 503 (Service Unavailable), and it

is

     inconvenient or impossible to generate a valid Date. 
  3. If the server does not have a clock that can provide a 
     reasonable approximation of the current time, its responses 
     MUST NOT include a Date header field. In this case, the rules 
     in section 14.18.1 MUST be followed.

Framework version: 1.1.1
Platform you're using: All

Reproduction steps:

Details:

Comments and changes to this ticket

Please Sign in or create a free account to add a new ticket.

With your very own profile, you can contribute to projects, track your activity, watch tickets, receive and update tickets through your email and much more.

New-ticket Create new ticket

Create your profile

Help contribute to this project by taking a few moments to create your personal profile. Create your profile »

<h2>Play framework</h2>

Play makes it easier to build Web applications with Java. It is a clean alternative to bloated Enterprise Java stacks. It focuses on developer productivity and targets RESTful architectures. Learn more on the <a href="http://www.playframework.org">http://www.playframework.org</a> website.<br><br>

<h2>Source code is hosted on github</h2>Check out our repository at <a href="http://github.com/playframework/play">http://github.com/playframework/play</a><br><br>

<h2>Contributing, creating a patch</h2> Please read the <a href="http://play.lighthouseapp.com/projects/57987/contributor-guide">contributor guide</a><br><br>

<h2>Reporting Security Vulnerabilities</h2> Since all bug reports are public, please report any security vulnerability directly to <em>guillaume dot bort at gmail dot com</em>.<br><br>

<h2>Creating a bug report</h2> Bug reports are incredibly helpful, so take time to report bugs and request features in our ticket tracker. We’re always grateful for patches to Play’s code. Indeed, bug reports with attached patches will get fixed far quickly than those without any.<br><br>

Please include as much relevant information as possible including the exact framework version you're using and a code snippet that reproduces the problem.<br><br>

Don't have too much expectations. Unless the bug is really a serious "everything is broken" thing, you're creating a ticket to start a discussion. Having a patch (or a branch on Github we can pull from) is better, but then again we'll only pull high quality branches that make sense to be in the core of Play.

People watching this ticket

Pages