[JIRA] [core] (JENKINS-17684) Dashboard web pages don't render correctly in Chrome because of bad cache/session

Tue, 21 May 2013 09:44:01 -0700

I think that a problem may be sending content-type header when http response is 304 in winstone.
Looking a capture http://imgur.com/9Y11bqz, css files are interpreted as 'text/html', but should be 'text/css'.

According to RFC, the 304 response should not include non-releated header.

If the conditional GET used a strong cache validator (see section 13.3.3), the response SHOULD NOT include other entity-headers. Otherwise (i.e., the conditional GET used a weak validator), the response MUST NOT include other entity-headers; this prevents inconsistencies between cached entity-bodies and updated headers.

For example, Plack ( which is web app framework by Perl ) excludes Content-Type / Content-Length / Content-Disposition headers.

So, I fix a source code to exclude content-type when 304, and trying it in my using Jenkins server.

If no problem for a week, I'll send a pull request this.
Currently, content-type header is normal and no problem occurs for three days.

It's ok that you fix in main repository source code before sending my pull request.
At which time, consider about other headers (Content-length, content-disposition, and so on), please.
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators.
For more information on JIRA, see: http://www.atlassian.com/software/jira

--
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/groups/opt_out.
 
 

Reply via email to