[
https://issues.apache.org/jira/browse/TS-824?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13112872#comment-13112872
]
William Bardwell commented on TS-824:
-------------------------------------
I looked at this, and it looks like HttpTransact::build_response_from_cache()'s
code when it gets HTTP_STATUS_NOT_MODIFIED(304) never tries to do
s->state_machine->do_range_setup_if_necessary();
(which it does do on status 200's), but there is a bunch of other range code
when status is 200 that might also need to be used in the 304 case.
> 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
>
>
> 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.
For more information on JIRA, see: http://www.atlassian.com/software/jira
