[
https://issues.jenkins-ci.org/browse/JENKINS-13125?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=162070#comment-162070
]
SCM/JIRA link daemon commented on JENKINS-13125:
------------------------------------------------
Code changed in jenkins
User: Kohsuke Kawaguchi
Path:
changelog.html
core/pom.xml
http://jenkins-ci.org/commit/jenkins/50593fb7aa158aa1b80a28159146d2f970ad1e98
Log:
[FIXED JENKINS-13125] Fixed a bug in Content-Range header handling
Compare: https://github.com/jenkinsci/jenkins/compare/047fdda...50593fb
> HTTP Content-Range Header one byte past file length
> ---------------------------------------------------
>
> Key: JENKINS-13125
> URL: https://issues.jenkins-ci.org/browse/JENKINS-13125
> Project: Jenkins
> Issue Type: Bug
> Components: www
> Affects Versions: current
> Reporter: Roland Schulz
>
> Downloading a PDF artifact using Chrome (17.0.963.79 m on Windows) the HTTP
> header for the last partial entity-body sent back by Jenkins contains:
> Content-Range: 2613923-2646691/2646691\r\n
> I believe this is wrong according to
> http://www.w3.org/Protocols/rfc2616/rfc2616-sec14.html#sec14.16 . I believe
> the last range should be 2613923-2646690/2646691, because the numbers are
> 0-indexed.
> I'm not sure whether this is caused by this or is a separate issue, but
> Chrome keeps requesting the same last partial segment and Jenkins returns the
> same one in an endless loop. Thus Chrome is stuck loading the PDF at 100% in
> the endless loop. This only happens with the Chrome embedded PDF viewer. The
> file downloads correctly with "Save as".
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators:
https://issues.jenkins-ci.org/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
