[jira] [Updated] (TS-2166) Response header to ua has two "Content-Range" field
[
https://issues.apache.org/jira/browse/TS-2166?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
portl4t updated TS-2166:
Description:
Follow these steps to reproduce:
1. TrafficServer cache a document which has "Etag" field in response header
2. The document expires.
3. UA sends request with "Range" field to this document.
4. TrafficServer sends request with IMS field to origin server to revalidate
this document
5. Origin Server sends response which has 304 code and "Content-Range" field to
TrafficServer
6. TrafficServer will generate another "Content-Range" field in RangeTransform.
{code}
HTTP/1.1 206 Partial Content
Date: Thu, 29 Aug 2013 03:09:05 GMT
Content-Type: application/octet-stream
Cache-Control: public
Content-Disposition: attachment;
Content-Encoding: utf-8
ETag: "F68ADB16DB4F1EF87D93D665CC1FFF54"
Expires: Tue,13 August 2013 07:04:10 GMT
Last-Modified: Tue, 13 Aug 2013 07:04:14 GMT
Server: ATS/3.2.0
x-oss-request-id: 521EBB51E369AA445D2F48B9
Accept-Ranges: bytes
Content-Range: bytes 0-4243537/4243538
Content-Range: bytes 0-4243537/4243538
Content-Length: 4243538
Age: 0
Via: http/1.1 l2cn202 (ATS [cSsNfU])
{code}
was:
Follow these steps to reproduce:
1. TrafficServer cache a document which has "Etag" field in response header
2. The document expires.
3. UA sends request with "Range" field to this document.
4. TrafficServer sends request with IMS field to origin server to revalidate
this document
5. Origin Server sends response which has 304 code and "Content-Range" field to
TrafficServer
6. TrafficServer will generate another "Content-Range" field in RangeTransform.
HTTP/1.1 206 Partial Content
Date: Thu, 29 Aug 2013 03:09:05 GMT
Content-Type: application/octet-stream
Cache-Control: public
Content-Disposition: attachment;
Content-Encoding: utf-8
ETag: "F68ADB16DB4F1EF87D93D665CC1FFF54"
Expires: Tue,13 August 2013 07:04:10 GMT
Last-Modified: Tue, 13 Aug 2013 07:04:14 GMT
Server: ATS/3.2.0
x-oss-request-id: 521EBB51E369AA445D2F48B9
Accept-Ranges: bytes
Content-Range: bytes 0-4243537/4243538
Content-Range: bytes 0-4243537/4243538
Content-Length: 4243538
Age: 0
Via: http/1.1 l2cn202 (ATS [cSsNfU])
> Response header to ua has two "Content-Range" field
> ---
>
> Key: TS-2166
> URL: https://issues.apache.org/jira/browse/TS-2166
> Project: Traffic Server
> Issue Type: Bug
> Components: HTTP
>Reporter: portl4t
>
> Follow these steps to reproduce:
> 1. TrafficServer cache a document which has "Etag" field in response header
> 2. The document expires.
> 3. UA sends request with "Range" field to this document.
> 4. TrafficServer sends request with IMS field to origin server to revalidate
> this document
> 5. Origin Server sends response which has 304 code and "Content-Range" field
> to TrafficServer
> 6. TrafficServer will generate another "Content-Range" field in
> RangeTransform.
> {code}
> HTTP/1.1 206 Partial Content
> Date: Thu, 29 Aug 2013 03:09:05 GMT
> Content-Type: application/octet-stream
> Cache-Control: public
> Content-Disposition: attachment;
> Content-Encoding: utf-8
> ETag: "F68ADB16DB4F1EF87D93D665CC1FFF54"
> Expires: Tue,13 August 2013 07:04:10 GMT
> Last-Modified: Tue, 13 Aug 2013 07:04:14 GMT
> Server: ATS/3.2.0
> x-oss-request-id: 521EBB51E369AA445D2F48B9
> Accept-Ranges: bytes
> Content-Range: bytes 0-4243537/4243538
> Content-Range: bytes 0-4243537/4243538
> Content-Length: 4243538
> Age: 0
> Via: http/1.1 l2cn202 (ATS [cSsNfU])
> {code}
--
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
[jira] [Updated] (TS-2166) Response header to ua has two "Content-Range" field
[
https://issues.apache.org/jira/browse/TS-2166?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
portl4t updated TS-2166:
Affects Version/s: 3.2.4
> Response header to ua has two "Content-Range" field
> ---
>
> Key: TS-2166
> URL: https://issues.apache.org/jira/browse/TS-2166
> Project: Traffic Server
> Issue Type: Bug
> Components: HTTP
>Affects Versions: 3.2.4
>Reporter: portl4t
>
> Follow these steps to reproduce:
> 1. TrafficServer cache a document which has "Etag" field in response header
> 2. The document expires.
> 3. UA sends request with "Range" field to this document.
> 4. TrafficServer sends request with IMS field to origin server to revalidate
> this document
> 5. Origin Server sends response which has 304 code and "Content-Range" field
> to TrafficServer
> 6. TrafficServer will generate another "Content-Range" field in
> RangeTransform.
> {code}
> HTTP/1.1 206 Partial Content
> Date: Thu, 29 Aug 2013 03:09:05 GMT
> Content-Type: application/octet-stream
> Cache-Control: public
> Content-Disposition: attachment;
> Content-Encoding: utf-8
> ETag: "F68ADB16DB4F1EF87D93D665CC1FFF54"
> Expires: Tue,13 August 2013 07:04:10 GMT
> Last-Modified: Tue, 13 Aug 2013 07:04:14 GMT
> Server: ATS/3.2.0
> x-oss-request-id: 521EBB51E369AA445D2F48B9
> Accept-Ranges: bytes
> Content-Range: bytes 0-4243537/4243538
> Content-Range: bytes 0-4243537/4243538
> Content-Length: 4243538
> Age: 0
> Via: http/1.1 l2cn202 (ATS [cSsNfU])
> {code}
--
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
[jira] [Updated] (TS-2166) Response header to ua has two "Content-Range" field
[
https://issues.apache.org/jira/browse/TS-2166?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Leif Hedstrom updated TS-2166:
--
Fix Version/s: 4.2.0
> Response header to ua has two "Content-Range" field
> ---
>
> Key: TS-2166
> URL: https://issues.apache.org/jira/browse/TS-2166
> Project: Traffic Server
> Issue Type: Bug
> Components: HTTP
>Affects Versions: 3.2.4, 4.2.0
>Reporter: portl4t
> Fix For: 4.2.0
>
>
> Follow these steps to reproduce:
> 1. TrafficServer cache a document which has "Etag" field in response header
> 2. The document expires.
> 3. UA sends request with "Range" field to this document.
> 4. TrafficServer sends request with IMS field to origin server to revalidate
> this document
> 5. Origin Server sends response which has 304 code and "Content-Range" field
> to TrafficServer
> 6. TrafficServer will generate another "Content-Range" field in
> RangeTransform.
> {code}
> HTTP/1.1 206 Partial Content
> Date: Thu, 29 Aug 2013 03:09:05 GMT
> Content-Type: application/octet-stream
> Cache-Control: public
> Content-Disposition: attachment;
> Content-Encoding: utf-8
> ETag: "F68ADB16DB4F1EF87D93D665CC1FFF54"
> Expires: Tue,13 August 2013 07:04:10 GMT
> Last-Modified: Tue, 13 Aug 2013 07:04:14 GMT
> Server: ATS/3.2.0
> x-oss-request-id: 521EBB51E369AA445D2F48B9
> Accept-Ranges: bytes
> Content-Range: bytes 0-4243537/4243538
> Content-Range: bytes 0-4243537/4243538
> Content-Length: 4243538
> Age: 0
> Via: http/1.1 l2cn202 (ATS [cSsNfU])
> {code}
--
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
[jira] [Updated] (TS-2166) Response header to ua has two "Content-Range" field
[
https://issues.apache.org/jira/browse/TS-2166?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Leif Hedstrom updated TS-2166:
--
Affects Version/s: 4.2.0
Marking as v4.2.0 for now, please please move / assign as appropriate.
> Response header to ua has two "Content-Range" field
> ---
>
> Key: TS-2166
> URL: https://issues.apache.org/jira/browse/TS-2166
> Project: Traffic Server
> Issue Type: Bug
> Components: HTTP
>Affects Versions: 3.2.4, 4.2.0
>Reporter: portl4t
>
> Follow these steps to reproduce:
> 1. TrafficServer cache a document which has "Etag" field in response header
> 2. The document expires.
> 3. UA sends request with "Range" field to this document.
> 4. TrafficServer sends request with IMS field to origin server to revalidate
> this document
> 5. Origin Server sends response which has 304 code and "Content-Range" field
> to TrafficServer
> 6. TrafficServer will generate another "Content-Range" field in
> RangeTransform.
> {code}
> HTTP/1.1 206 Partial Content
> Date: Thu, 29 Aug 2013 03:09:05 GMT
> Content-Type: application/octet-stream
> Cache-Control: public
> Content-Disposition: attachment;
> Content-Encoding: utf-8
> ETag: "F68ADB16DB4F1EF87D93D665CC1FFF54"
> Expires: Tue,13 August 2013 07:04:10 GMT
> Last-Modified: Tue, 13 Aug 2013 07:04:14 GMT
> Server: ATS/3.2.0
> x-oss-request-id: 521EBB51E369AA445D2F48B9
> Accept-Ranges: bytes
> Content-Range: bytes 0-4243537/4243538
> Content-Range: bytes 0-4243537/4243538
> Content-Length: 4243538
> Age: 0
> Via: http/1.1 l2cn202 (ATS [cSsNfU])
> {code}
--
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
[jira] [Updated] (TS-2166) Response header to ua has two "Content-Range" field
[
https://issues.apache.org/jira/browse/TS-2166?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
portl4t updated TS-2166:
Assignee: portl4t
> Response header to ua has two "Content-Range" field
> ---
>
> Key: TS-2166
> URL: https://issues.apache.org/jira/browse/TS-2166
> Project: Traffic Server
> Issue Type: Bug
> Components: HTTP
>Affects Versions: 3.2.4, 4.2.0
>Reporter: portl4t
>Assignee: portl4t
> Fix For: 4.2.0
>
>
> Follow these steps to reproduce:
> 1. TrafficServer cache a document which has "Etag" field in response header
> 2. The document expires.
> 3. UA sends request with "Range" field to this document.
> 4. TrafficServer sends request with IMS field to origin server to revalidate
> this document
> 5. Origin Server sends response which has 304 code and "Content-Range" field
> to TrafficServer
> 6. TrafficServer will generate another "Content-Range" field in
> RangeTransform.
> {code}
> HTTP/1.1 206 Partial Content
> Date: Thu, 29 Aug 2013 03:09:05 GMT
> Content-Type: application/octet-stream
> Cache-Control: public
> Content-Disposition: attachment;
> Content-Encoding: utf-8
> ETag: "F68ADB16DB4F1EF87D93D665CC1FFF54"
> Expires: Tue,13 August 2013 07:04:10 GMT
> Last-Modified: Tue, 13 Aug 2013 07:04:14 GMT
> Server: ATS/3.2.0
> x-oss-request-id: 521EBB51E369AA445D2F48B9
> Accept-Ranges: bytes
> Content-Range: bytes 0-4243537/4243538
> Content-Range: bytes 0-4243537/4243538
> Content-Length: 4243538
> Age: 0
> Via: http/1.1 l2cn202 (ATS [cSsNfU])
> {code}
--
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
[jira] [Updated] (TS-2166) Response header to ua has two "Content-Range" field
[
https://issues.apache.org/jira/browse/TS-2166?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Susan Hinrichs updated TS-2166:
---
Assignee: (was: portl4t)
> Response header to ua has two "Content-Range" field
> ---
>
> Key: TS-2166
> URL: https://issues.apache.org/jira/browse/TS-2166
> Project: Traffic Server
> Issue Type: Bug
> Components: HTTP
>Affects Versions: 3.2.4, 4.2.0
>Reporter: portl4t
> Fix For: 5.2.0
>
>
> Follow these steps to reproduce:
> 1. TrafficServer cache a document which has "Etag" field in response header
> 2. The document expires.
> 3. UA sends request with "Range" field to this document.
> 4. TrafficServer sends request with IMS field to origin server to revalidate
> this document
> 5. Origin Server sends response which has 304 code and "Content-Range" field
> to TrafficServer
> 6. TrafficServer will generate another "Content-Range" field in
> RangeTransform.
> {code}
> HTTP/1.1 206 Partial Content
> Date: Thu, 29 Aug 2013 03:09:05 GMT
> Content-Type: application/octet-stream
> Cache-Control: public
> Content-Disposition: attachment;
> Content-Encoding: utf-8
> ETag: "F68ADB16DB4F1EF87D93D665CC1FFF54"
> Expires: Tue,13 August 2013 07:04:10 GMT
> Last-Modified: Tue, 13 Aug 2013 07:04:14 GMT
> Server: ATS/3.2.0
> x-oss-request-id: 521EBB51E369AA445D2F48B9
> Accept-Ranges: bytes
> Content-Range: bytes 0-4243537/4243538
> Content-Range: bytes 0-4243537/4243538
> Content-Length: 4243538
> Age: 0
> Via: http/1.1 l2cn202 (ATS [cSsNfU])
> {code}
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Updated] (TS-2166) Response header to ua has two "Content-Range" field
[
https://issues.apache.org/jira/browse/TS-2166?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Susan Hinrichs updated TS-2166:
---
Fix Version/s: (was: 5.2.0)
5.3.0
> Response header to ua has two "Content-Range" field
> ---
>
> Key: TS-2166
> URL: https://issues.apache.org/jira/browse/TS-2166
> Project: Traffic Server
> Issue Type: Bug
> Components: HTTP
>Affects Versions: 3.2.4, 4.2.0
>Reporter: portl4t
> Fix For: 5.3.0
>
>
> Follow these steps to reproduce:
> 1. TrafficServer cache a document which has "Etag" field in response header
> 2. The document expires.
> 3. UA sends request with "Range" field to this document.
> 4. TrafficServer sends request with IMS field to origin server to revalidate
> this document
> 5. Origin Server sends response which has 304 code and "Content-Range" field
> to TrafficServer
> 6. TrafficServer will generate another "Content-Range" field in
> RangeTransform.
> {code}
> HTTP/1.1 206 Partial Content
> Date: Thu, 29 Aug 2013 03:09:05 GMT
> Content-Type: application/octet-stream
> Cache-Control: public
> Content-Disposition: attachment;
> Content-Encoding: utf-8
> ETag: "F68ADB16DB4F1EF87D93D665CC1FFF54"
> Expires: Tue,13 August 2013 07:04:10 GMT
> Last-Modified: Tue, 13 Aug 2013 07:04:14 GMT
> Server: ATS/3.2.0
> x-oss-request-id: 521EBB51E369AA445D2F48B9
> Accept-Ranges: bytes
> Content-Range: bytes 0-4243537/4243538
> Content-Range: bytes 0-4243537/4243538
> Content-Length: 4243538
> Age: 0
> Via: http/1.1 l2cn202 (ATS [cSsNfU])
> {code}
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Updated] (TS-2166) Response header to ua has two "Content-Range" field
[
https://issues.apache.org/jira/browse/TS-2166?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Alan M. Carroll updated TS-2166:
Fix Version/s: (was: 6.1.0)
6.2.0
> Response header to ua has two "Content-Range" field
> ---
>
> Key: TS-2166
> URL: https://issues.apache.org/jira/browse/TS-2166
> Project: Traffic Server
> Issue Type: Bug
> Components: HTTP
>Affects Versions: 3.2.4, 4.2.0
>Reporter: portl4t
>Assignee: Alan M. Carroll
> Fix For: 6.2.0
>
>
> Follow these steps to reproduce:
> 1. TrafficServer cache a document which has "Etag" field in response header
> 2. The document expires.
> 3. UA sends request with "Range" field to this document.
> 4. TrafficServer sends request with IMS field to origin server to revalidate
> this document
> 5. Origin Server sends response which has 304 code and "Content-Range" field
> to TrafficServer
> 6. TrafficServer will generate another "Content-Range" field in
> RangeTransform.
> {code}
> HTTP/1.1 206 Partial Content
> Date: Thu, 29 Aug 2013 03:09:05 GMT
> Content-Type: application/octet-stream
> Cache-Control: public
> Content-Disposition: attachment;
> Content-Encoding: utf-8
> ETag: "F68ADB16DB4F1EF87D93D665CC1FFF54"
> Expires: Tue,13 August 2013 07:04:10 GMT
> Last-Modified: Tue, 13 Aug 2013 07:04:14 GMT
> Server: ATS/3.2.0
> x-oss-request-id: 521EBB51E369AA445D2F48B9
> Accept-Ranges: bytes
> Content-Range: bytes 0-4243537/4243538
> Content-Range: bytes 0-4243537/4243538
> Content-Length: 4243538
> Age: 0
> Via: http/1.1 l2cn202 (ATS [cSsNfU])
> {code}
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Updated] (TS-2166) Response header to ua has two "Content-Range" field
[
https://issues.apache.org/jira/browse/TS-2166?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Leif Hedstrom updated TS-2166:
--
Fix Version/s: (was: 6.2.0)
7.0.0
> Response header to ua has two "Content-Range" field
> ---
>
> Key: TS-2166
> URL: https://issues.apache.org/jira/browse/TS-2166
> Project: Traffic Server
> Issue Type: Bug
> Components: HTTP
>Affects Versions: 3.2.4, 4.2.0
>Reporter: portl4t
>Assignee: Alan M. Carroll
> Fix For: 7.0.0
>
>
> Follow these steps to reproduce:
> 1. TrafficServer cache a document which has "Etag" field in response header
> 2. The document expires.
> 3. UA sends request with "Range" field to this document.
> 4. TrafficServer sends request with IMS field to origin server to revalidate
> this document
> 5. Origin Server sends response which has 304 code and "Content-Range" field
> to TrafficServer
> 6. TrafficServer will generate another "Content-Range" field in
> RangeTransform.
> {code}
> HTTP/1.1 206 Partial Content
> Date: Thu, 29 Aug 2013 03:09:05 GMT
> Content-Type: application/octet-stream
> Cache-Control: public
> Content-Disposition: attachment;
> Content-Encoding: utf-8
> ETag: "F68ADB16DB4F1EF87D93D665CC1FFF54"
> Expires: Tue,13 August 2013 07:04:10 GMT
> Last-Modified: Tue, 13 Aug 2013 07:04:14 GMT
> Server: ATS/3.2.0
> x-oss-request-id: 521EBB51E369AA445D2F48B9
> Accept-Ranges: bytes
> Content-Range: bytes 0-4243537/4243538
> Content-Range: bytes 0-4243537/4243538
> Content-Length: 4243538
> Age: 0
> Via: http/1.1 l2cn202 (ATS [cSsNfU])
> {code}
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Updated] (TS-2166) Response header to ua has two "Content-Range" field
[
https://issues.apache.org/jira/browse/TS-2166?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Bryan Call updated TS-2166:
---
Fix Version/s: (was: 7.0.0)
7.2.0
> Response header to ua has two "Content-Range" field
> ---
>
> Key: TS-2166
> URL: https://issues.apache.org/jira/browse/TS-2166
> Project: Traffic Server
> Issue Type: Bug
> Components: HTTP
>Affects Versions: 3.2.4, 4.2.0
>Reporter: portl4t
>Assignee: Alan M. Carroll
> Fix For: 7.2.0
>
>
> Follow these steps to reproduce:
> 1. TrafficServer cache a document which has "Etag" field in response header
> 2. The document expires.
> 3. UA sends request with "Range" field to this document.
> 4. TrafficServer sends request with IMS field to origin server to revalidate
> this document
> 5. Origin Server sends response which has 304 code and "Content-Range" field
> to TrafficServer
> 6. TrafficServer will generate another "Content-Range" field in
> RangeTransform.
> {code}
> HTTP/1.1 206 Partial Content
> Date: Thu, 29 Aug 2013 03:09:05 GMT
> Content-Type: application/octet-stream
> Cache-Control: public
> Content-Disposition: attachment;
> Content-Encoding: utf-8
> ETag: "F68ADB16DB4F1EF87D93D665CC1FFF54"
> Expires: Tue,13 August 2013 07:04:10 GMT
> Last-Modified: Tue, 13 Aug 2013 07:04:14 GMT
> Server: ATS/3.2.0
> x-oss-request-id: 521EBB51E369AA445D2F48B9
> Accept-Ranges: bytes
> Content-Range: bytes 0-4243537/4243538
> Content-Range: bytes 0-4243537/4243538
> Content-Length: 4243538
> Age: 0
> Via: http/1.1 l2cn202 (ATS [cSsNfU])
> {code}
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Updated] (TS-2166) Response header to ua has two "Content-Range" field
[
https://issues.apache.org/jira/browse/TS-2166?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Phil Sorber updated TS-2166:
Assignee: Alan M. Carroll
> Response header to ua has two "Content-Range" field
> ---
>
> Key: TS-2166
> URL: https://issues.apache.org/jira/browse/TS-2166
> Project: Traffic Server
> Issue Type: Bug
> Components: HTTP
>Affects Versions: 3.2.4, 4.2.0
>Reporter: portl4t
>Assignee: Alan M. Carroll
> Fix For: 6.0.0
>
>
> Follow these steps to reproduce:
> 1. TrafficServer cache a document which has "Etag" field in response header
> 2. The document expires.
> 3. UA sends request with "Range" field to this document.
> 4. TrafficServer sends request with IMS field to origin server to revalidate
> this document
> 5. Origin Server sends response which has 304 code and "Content-Range" field
> to TrafficServer
> 6. TrafficServer will generate another "Content-Range" field in
> RangeTransform.
> {code}
> HTTP/1.1 206 Partial Content
> Date: Thu, 29 Aug 2013 03:09:05 GMT
> Content-Type: application/octet-stream
> Cache-Control: public
> Content-Disposition: attachment;
> Content-Encoding: utf-8
> ETag: "F68ADB16DB4F1EF87D93D665CC1FFF54"
> Expires: Tue,13 August 2013 07:04:10 GMT
> Last-Modified: Tue, 13 Aug 2013 07:04:14 GMT
> Server: ATS/3.2.0
> x-oss-request-id: 521EBB51E369AA445D2F48B9
> Accept-Ranges: bytes
> Content-Range: bytes 0-4243537/4243538
> Content-Range: bytes 0-4243537/4243538
> Content-Length: 4243538
> Age: 0
> Via: http/1.1 l2cn202 (ATS [cSsNfU])
> {code}
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Updated] (TS-2166) Response header to ua has two "Content-Range" field
[
https://issues.apache.org/jira/browse/TS-2166?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Phil Sorber updated TS-2166:
Fix Version/s: (was: 6.0.0)
6.1.0
> Response header to ua has two "Content-Range" field
> ---
>
> Key: TS-2166
> URL: https://issues.apache.org/jira/browse/TS-2166
> Project: Traffic Server
> Issue Type: Bug
> Components: HTTP
>Affects Versions: 3.2.4, 4.2.0
>Reporter: portl4t
>Assignee: Alan M. Carroll
> Fix For: 6.1.0
>
>
> Follow these steps to reproduce:
> 1. TrafficServer cache a document which has "Etag" field in response header
> 2. The document expires.
> 3. UA sends request with "Range" field to this document.
> 4. TrafficServer sends request with IMS field to origin server to revalidate
> this document
> 5. Origin Server sends response which has 304 code and "Content-Range" field
> to TrafficServer
> 6. TrafficServer will generate another "Content-Range" field in
> RangeTransform.
> {code}
> HTTP/1.1 206 Partial Content
> Date: Thu, 29 Aug 2013 03:09:05 GMT
> Content-Type: application/octet-stream
> Cache-Control: public
> Content-Disposition: attachment;
> Content-Encoding: utf-8
> ETag: "F68ADB16DB4F1EF87D93D665CC1FFF54"
> Expires: Tue,13 August 2013 07:04:10 GMT
> Last-Modified: Tue, 13 Aug 2013 07:04:14 GMT
> Server: ATS/3.2.0
> x-oss-request-id: 521EBB51E369AA445D2F48B9
> Accept-Ranges: bytes
> Content-Range: bytes 0-4243537/4243538
> Content-Range: bytes 0-4243537/4243538
> Content-Length: 4243538
> Age: 0
> Via: http/1.1 l2cn202 (ATS [cSsNfU])
> {code}
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
