[
https://issues.apache.org/jira/browse/TS-824?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Leif Hedstrom updated TS-824:
-----------------------------
Attachment: TS-824.diff
Here's something that solves at least some of the problem... Feedback and
comments appreciated.
> Range requests that result in cache refresh give 200 status response with
> full contents
> ---------------------------------------------------------------------------------------
>
> Key: TS-824
> URL: https://issues.apache.org/jira/browse/TS-824
> Project: Traffic Server
> Issue Type: Bug
> Components: HTTP
> Affects Versions: 2.1.9, 2.1.8, 2.1.7, 2.1.6, 2.1.5, 2.1.4
> Reporter: William Bardwell
> Priority: Minor
> Fix For: 3.1.1
>
> Attachments: TS-824.diff
>
>
> If you send a request with a Range: header to TS when it has full cached
> contents that need to be refreshed, and they get back a status 304 response
> indicating that the cached contents are up to date, TS will respond to the
> client with a status 200 response, and the full contents. So the content is
> served from cache, but do not go through the transform to only return partial
> bytes and a status 206 response like it should.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators:
https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
