[jira] [Updated] (TS-3917) Sending only SETTINGS_INITIAL_WINDOW_SIZE in SETTINGS Frame
[
https://issues.apache.org/jira/browse/TS-3917?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Leif Hedstrom updated TS-3917:
--
Assignee: Bryan Call
> Sending only SETTINGS_INITIAL_WINDOW_SIZE in SETTINGS Frame
> ---
>
> Key: TS-3917
> URL: https://issues.apache.org/jira/browse/TS-3917
> Project: Traffic Server
> Issue Type: Bug
> Components: HTTP/2
>Reporter: Masaori Koshiba
>Assignee: Bryan Call
>Priority: Critical
> Fix For: 6.0.1
>
>
> After fix for TS-3492, ATS sends only {{SETTINGS_INITIAL_WINDOW_SIZE}} in
> first SETTINGS Frame.
> ATS should send SETTINGS Parameters when values in records.config is
> different from default value of RFC7540 (6.5.2 Defined SETTINGS Parameters).
> For example, {{SETTINGS_MAX_CONCURRENT_STREAMS}} is unlimited in RFC7540, but
> default value in records.config is 100. ATS should send this value in first
> SETTINGS Frame but not.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Updated] (TS-3946) Invalid pad length in HTTP/2
[
https://issues.apache.org/jira/browse/TS-3946?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Leif Hedstrom updated TS-3946:
--
Assignee: (was: Leif Hedstrom)
> Invalid pad length in HTTP/2
>
>
> Key: TS-3946
> URL: https://issues.apache.org/jira/browse/TS-3946
> Project: Traffic Server
> Issue Type: Bug
> Components: HTTP/2
>Reporter: Leif Hedstrom
> Fix For: 6.1.0
>
>
> This is an h2spec issue:
> {code}
> 6.1. DATA
> ✓ Sends a DATA frame with 0x0 stream identifier
> ✓ Sends a DATA frame on the stream that is not opend
> × Sends a DATA frame with invalid pad length
> - The endpoint MUST treat this as a connection error of type
> PROTOCOL_ERROR.
> Expected: GOAWAY frame (ErrorCode: PROTOCOL_ERROR)
> RST_STREAM frame (ErrorCode: PROTOCOL_ERROR)
> Connection close
> Actual: RST_STREAM frame (Length: 4, Flags: 0, ErrorCode:
> STREAM_CLOSED)
> {code}
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Commented] (TS-3864) Ability to shed traffic with HTTP/2
[ https://issues.apache.org/jira/browse/TS-3864?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14993315#comment-14993315 ] Bryan Call commented on TS-3864: It might be better to use the traffic_ctl command and --drain to do this. > Ability to shed traffic with HTTP/2 > --- > > Key: TS-3864 > URL: https://issues.apache.org/jira/browse/TS-3864 > Project: Traffic Server > Issue Type: Improvement > Components: HTTP/2 >Reporter: Bryan Call > Labels: yahoo > Fix For: 6.1.0 > > > Add a new configuration option to ATS > (proxy.config.http2.shutdown_connections) that can be toggled to allow > administrators the ability to close all existing HTTP/2 connections. When > this option is on a GOAWAY frame would be sent to all the HTTP/2 connections > so they can gracefully shutdown. The RFC covers this scenario. > https://tools.ietf.org/html/rfc7540#section-6.8 -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (TS-3917) Sending only SETTINGS_INITIAL_WINDOW_SIZE in SETTINGS Frame
[
https://issues.apache.org/jira/browse/TS-3917?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Leif Hedstrom updated TS-3917:
--
Priority: Critical (was: Major)
> Sending only SETTINGS_INITIAL_WINDOW_SIZE in SETTINGS Frame
> ---
>
> Key: TS-3917
> URL: https://issues.apache.org/jira/browse/TS-3917
> Project: Traffic Server
> Issue Type: Bug
> Components: HTTP/2
>Reporter: Masaori Koshiba
>Priority: Critical
> Fix For: 6.0.1
>
>
> After fix for TS-3492, ATS sends only {{SETTINGS_INITIAL_WINDOW_SIZE}} in
> first SETTINGS Frame.
> ATS should send SETTINGS Parameters when values in records.config is
> different from default value of RFC7540 (6.5.2 Defined SETTINGS Parameters).
> For example, {{SETTINGS_MAX_CONCURRENT_STREAMS}} is unlimited in RFC7540, but
> default value in records.config is 100. ATS should send this value in first
> SETTINGS Frame but not.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Updated] (TS-3847) Rejects Dynamic Table Size if it does not appear at the beginning of the first header block
[
https://issues.apache.org/jira/browse/TS-3847?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Leif Hedstrom updated TS-3847:
--
Assignee: Masaori Koshiba
> Rejects Dynamic Table Size if it does not appear at the beginning of the
> first header block
> ---
>
> Key: TS-3847
> URL: https://issues.apache.org/jira/browse/TS-3847
> Project: Traffic Server
> Issue Type: Bug
> Components: HTTP/2
>Reporter: Masaori Koshiba
>Assignee: Masaori Koshiba
> Fix For: 6.1.0
>
>
> Section 4.2 of RFC 7541(HPACK), says that dynamic table size update MUST
> occur at the beginning of the first header block following the changes to the
> dynamic table size.
> {code}
> ===
> Failed tests
> ===
> 4.3. Header Compression and Decompression
> × Encodes Dynamic Table Size Update (RFC 7541, 6.3) after common header
> fields
> - The endpoint MUST terminate the connection with a connection error of
> type COMPRESSION_ERROR.
> Expected: GOAWAY frame (ErrorCode: COMPRESSION_ERROR)
> Connection close
> Actual: DATA frame (Length: 5991, Flags: 1)
> {code}
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Commented] (TS-3843) Strange framing should be handled as usual
[ https://issues.apache.org/jira/browse/TS-3843?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14993304#comment-14993304 ] Leif Hedstrom commented on TS-3843: --- [~maskit] Please send patch , and [~bcall] will buy you beer. > Strange framing should be handled as usual > -- > > Key: TS-3843 > URL: https://issues.apache.org/jira/browse/TS-3843 > Project: Traffic Server > Issue Type: Improvement > Components: HTTP/2 >Reporter: Masakazu Kitajo > Fix For: 6.1.0 > > > To put all header fields into CONTINUATION frames is not prohibited, however, > TS treat this framing as a protocol error. > Though such a framing is inefficient and would not be used by ordinary > clients, it should be handled in the same way as normal cases. Because it can > be used for server fingerprinting. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (TS-3995) "[hcoofsr] conditional request, 200 response, send back 304 if possible [crc=304]" breaks akamaihd.net live streaming
[
https://issues.apache.org/jira/browse/TS-3995?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Nikolai Gorchilov updated TS-3995:
--
Description:
Caching proxy running ATS 5.3.x (5.3.0, 5.3.1, 5.3.2 all fail) with
proxy.config.http.cache.when_to_revalidate = 4 breaks akamaihd.net live
streaming.
The actual problem is that ATS rewrites origin response from 200 to 304, due to
If-Modified-Since conditional header in client's request. As per ATS logic
object is unmodified, but in fact it is. Most probably player and server
somehow play with if-modified-since/last-modified headers pair to communicate
position in the live stream. What is obvious is that Last-Modified =
If-Modified-Since.
As result, Akamai player keeps repeating the said request, expecting it's 200,
but getting 304 thus live video freezes forever, just a few seconds after start.
IMHO when proxy.config.http.cache.when_to_revalidate = 4, ATS shall not
interfere with origin response in this manner.
Here's a debug log of request and response headers at different states in a
single transaction:
{noformat}
+ Incoming Request +
-- State Machine Id: 168
GET
http:///z/delayed/indvsa2015_INDVSSATEST1DAY1_1@336263/464_209823ecd2922291-p.bootstrap?g=YCEAMIWDQZQT&hdntl=exp=1446809835~acl=%2f*~data=hdntl~hmac=ebaedb13781605ce7f9f26b84e1346a7d43ecf0dfcc99e6b53e32487565ba3f8&hdcore=3.7.0&plugin=aasp-3.7.0.39.44
HTTP/1.1
Host: sshds5-lh.akamaihd.net
Connection: keep-alive
User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10_11_1) AppleWebKit/537.36
(KHTML, like Gecko) Chrome/46.0.2490.80 Safari/537.36
X-Requested-With: ShockwaveFlash/19.0.0.226
Accept: */*
DNT: 1
Referer: http://www.hotstar.com/
Accept-Encoding: gzip
Accept-Language: en-US,en;q=0.8,bg;q=0.6
Cookie: _alid_=PmjLqgcUUqw6TP5gtK/xbg==;
hdntl=exp=1446809835~acl=%2f*~data=hdntl~hmac=ebaedb13781605ce7f9f26b84e1346a7d43ecf0dfcc99e6b53e32487565ba3f8
If-Modified-Since: Thu, 05 Nov 2015 02:30:28 GMT
+ Proxy's Request +
-- State Machine Id: 168
GET
/z/delayed/indvsa2015_INDVSSATEST1DAY1_1@336263/464_209823ecd2922291-p.bootstrap?g=YCEAMIWDQZQT&hdntl=exp=1446809835~acl=%2f*~data=hdntl~hmac=ebaedb13781605ce7f9f26b84e1346a7d43ecf0dfcc99e6b53e32487565ba3f8&hdcore=3.7.0&plugin=aasp-3.7.0.39.44
HTTP/1.1
Host: sshds5-lh.akamaihd.net
User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10_11_1) AppleWebKit/537.36
(KHTML, like Gecko) Chrome/46.0.2490.80 Safari/537.36
X-Requested-With: ShockwaveFlash/19.0.0.226
Accept: */*
DNT: 1
Referer: http://www.hotstar.com/
Accept-Encoding: gzip
Accept-Language: en-US,en;q=0.8,bg;q=0.6
Cookie: _alid_=PmjLqgcUUqw6TP5gtK/xbg==;
hdntl=exp=1446809835~acl=%2f*~data=hdntl~hmac=ebaedb13781605ce7f9f26b84e1346a7d43ecf0dfcc99e6b53e32487565ba3f8
If-Modified-Since: Thu, 05 Nov 2015 02:30:28 GMT
+ Proxy's Request after hooks +
-- State Machine Id: 168
GET
/z/delayed/indvsa2015_INDVSSATEST1DAY1_1@336263/464_209823ecd2922291-p.bootstrap?g=YCEAMIWDQZQT&hdntl=exp=1446809835~acl=%2f*~data=hdntl~hmac=ebaedb13781605ce7f9f26b84e1346a7d43ecf0dfcc99e6b53e32487565ba3f8&hdcore=3.7.0&plugin=aasp-3.7.0.39.44
HTTP/1.1
Host: sshds5-lh.akamaihd.net
User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10_11_1) AppleWebKit/537.36
(KHTML, like Gecko) Chrome/46.0.2490.80 Safari/537.36
X-Requested-With: ShockwaveFlash/19.0.0.226
Accept: */*
DNT: 1
Referer: http://www.hotstar.com/
Accept-Encoding: gzip
Accept-Language: en-US,en;q=0.8,bg;q=0.6
Cookie: _alid_=PmjLqgcUUqw6TP5gtK/xbg==;
hdntl=exp=1446809835~acl=%2f*~data=hdntl~hmac=ebaedb13781605ce7f9f26b84e1346a7d43ecf0dfcc99e6b53e32487565ba3f8
If-Modified-Since: Thu, 05 Nov 2015 02:30:28 GMT
+ Incoming O.S. Response +
-- State Machine Id: 168
HTTP/1.1 200 OK
Server: AkamaiGHost
Mime-Version: 1.0
Content-Type: video/abst
Content-Length: 122
Last-Modified: Thu, 05 Nov 2015 02:30:28 GMT
Expires: Thu, 05 Nov 2015 11:38:01 GMT
Cache-Control: max-age=0, no-cache
Pragma: no-cache
Date: Thu, 05 Nov 2015 11:38:01 GMT
Connection: keep-alive
Set-Cookie: _alid_=PmjLqgcUUqw6TP5gtK/xbg==;
path=/z/delayed/indvsa2015_INDVSSATEST1DAY1_1@336263/;
domain=sshds5-lh.akamaihd.net
+ Base Header for Building Response +
-- State Machine Id: 168
HTTP/1.1 200 OK
Server: AkamaiGHost
Mime-Version: 1.0
Content-Type: video/abst
Content-Length: 122
Last-Modified: Thu, 05 Nov 2015 02:30:28 GMT
Expires: Thu, 05 Nov 2015 11:38:01 GMT
Cache-Control: max-age=0, no-cache
Pragma: no-cache
Date: Thu, 05 Nov 2015 11:38:01 GMT
Connection: keep-alive
Set-Cookie: _alid_=PmjLqgcUUqw6TP5gtK/xbg==;
path=/z/delayed/indvsa2015_INDVSSATEST1DAY1_1@336263/;
domain=sshds5-lh.akamaihd.net
+ Proxy's Response 2 +
-- State Machine Id: 168
HTTP/1.1 304 Not Modified
Date: Thu, 05 Nov 2015 11:38:01 GMT
Expires: Thu, 05 Nov 2015 11:38:01 GMT
Cache-Control: max-age=0, no-cache
Connection: keep-alive
+ Proxy's Response (Client Co
[jira] [Commented] (TS-3789) If HTTP/2 is negotiated, TLS compression must be disabled
[ https://issues.apache.org/jira/browse/TS-3789?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14993299#comment-14993299 ] Bryan Call commented on TS-3789: A deployment of HTTP/2 over TLS 1.2 MUST disable compression. > If HTTP/2 is negotiated, TLS compression must be disabled > - > > Key: TS-3789 > URL: https://issues.apache.org/jira/browse/TS-3789 > Project: Traffic Server > Issue Type: Bug > Components: HTTP/2 >Reporter: Leif Hedstrom > Fix For: 6.1.0 > > > Per https://tools.ietf.org/html/rfc7540#section-9.2. Couple of options: > 1) Make these overridable / configurable per protocol. > 2) Basically make proxy.config.ssl.compression=0 always if HTTP/2 is enabled. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (TS-3787) Don't allow blacklisted HTTP/2 ciphers to use HTTP/2
[ https://issues.apache.org/jira/browse/TS-3787?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Leif Hedstrom updated TS-3787: -- Fix Version/s: (was: 6.1.0) sometime > Don't allow blacklisted HTTP/2 ciphers to use HTTP/2 > > > Key: TS-3787 > URL: https://issues.apache.org/jira/browse/TS-3787 > Project: Traffic Server > Issue Type: Improvement > Components: HTTP/2 >Reporter: Bryan Call > Labels: yahoo > Fix For: sometime > > > Look at the selected cipher and if it is on the blacklist then don't allow > the client to use HTTP/2. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (TS-3995) "[hcoofsr] conditional request, 200 response, send back 304 if possible [crc=304]" breaks akamaihd.net live streaming
[
https://issues.apache.org/jira/browse/TS-3995?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Nikolai Gorchilov updated TS-3995:
--
Description:
Caching proxy running ATS 5.3.x (5.3.0, 5.3.1, 5.3.2 all fail) with
proxy.config.http.cache.when_to_revalidate = 4 breaks akamaihd.net live
streaming.
The actual problem is that ATS rewrites origin response from 200 to 304, due to
If-Modified-Since conditional header in client's request. As per ATS logic
object is unmodified, but in fact it is. Most probably it's related to the fact
that player and server somehow play with if-modified-since/last-modified
headers pair to communicate position in the live stream.
As result, Akamai player keeps repeating the said request, expecting it's 200,
but getting 304 thus live video freezes forever, just a few seconds after start.
IMHO when proxy.config.http.cache.when_to_revalidate = 4, ATS shall not
interfere with origin response in this manner.
Here's a debug log of request and response headers at different states in a
single transaction:
{noformat}
+ Incoming Request +
-- State Machine Id: 168
GET
http:///z/delayed/indvsa2015_INDVSSATEST1DAY1_1@336263/464_209823ecd2922291-p.bootstrap?g=YCEAMIWDQZQT&hdntl=exp=1446809835~acl=%2f*~data=hdntl~hmac=ebaedb13781605ce7f9f26b84e1346a7d43ecf0dfcc99e6b53e32487565ba3f8&hdcore=3.7.0&plugin=aasp-3.7.0.39.44
HTTP/1.1
Host: sshds5-lh.akamaihd.net
Connection: keep-alive
User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10_11_1) AppleWebKit/537.36
(KHTML, like Gecko) Chrome/46.0.2490.80 Safari/537.36
X-Requested-With: ShockwaveFlash/19.0.0.226
Accept: */*
DNT: 1
Referer: http://www.hotstar.com/
Accept-Encoding: gzip
Accept-Language: en-US,en;q=0.8,bg;q=0.6
Cookie: _alid_=PmjLqgcUUqw6TP5gtK/xbg==;
hdntl=exp=1446809835~acl=%2f*~data=hdntl~hmac=ebaedb13781605ce7f9f26b84e1346a7d43ecf0dfcc99e6b53e32487565ba3f8
If-Modified-Since: Thu, 05 Nov 2015 02:30:28 GMT
+ Proxy's Request +
-- State Machine Id: 168
GET
/z/delayed/indvsa2015_INDVSSATEST1DAY1_1@336263/464_209823ecd2922291-p.bootstrap?g=YCEAMIWDQZQT&hdntl=exp=1446809835~acl=%2f*~data=hdntl~hmac=ebaedb13781605ce7f9f26b84e1346a7d43ecf0dfcc99e6b53e32487565ba3f8&hdcore=3.7.0&plugin=aasp-3.7.0.39.44
HTTP/1.1
Host: sshds5-lh.akamaihd.net
User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10_11_1) AppleWebKit/537.36
(KHTML, like Gecko) Chrome/46.0.2490.80 Safari/537.36
X-Requested-With: ShockwaveFlash/19.0.0.226
Accept: */*
DNT: 1
Referer: http://www.hotstar.com/
Accept-Encoding: gzip
Accept-Language: en-US,en;q=0.8,bg;q=0.6
Cookie: _alid_=PmjLqgcUUqw6TP5gtK/xbg==;
hdntl=exp=1446809835~acl=%2f*~data=hdntl~hmac=ebaedb13781605ce7f9f26b84e1346a7d43ecf0dfcc99e6b53e32487565ba3f8
If-Modified-Since: Thu, 05 Nov 2015 02:30:28 GMT
+ Proxy's Request after hooks +
-- State Machine Id: 168
GET
/z/delayed/indvsa2015_INDVSSATEST1DAY1_1@336263/464_209823ecd2922291-p.bootstrap?g=YCEAMIWDQZQT&hdntl=exp=1446809835~acl=%2f*~data=hdntl~hmac=ebaedb13781605ce7f9f26b84e1346a7d43ecf0dfcc99e6b53e32487565ba3f8&hdcore=3.7.0&plugin=aasp-3.7.0.39.44
HTTP/1.1
Host: sshds5-lh.akamaihd.net
User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10_11_1) AppleWebKit/537.36
(KHTML, like Gecko) Chrome/46.0.2490.80 Safari/537.36
X-Requested-With: ShockwaveFlash/19.0.0.226
Accept: */*
DNT: 1
Referer: http://www.hotstar.com/
Accept-Encoding: gzip
Accept-Language: en-US,en;q=0.8,bg;q=0.6
Cookie: _alid_=PmjLqgcUUqw6TP5gtK/xbg==;
hdntl=exp=1446809835~acl=%2f*~data=hdntl~hmac=ebaedb13781605ce7f9f26b84e1346a7d43ecf0dfcc99e6b53e32487565ba3f8
If-Modified-Since: Thu, 05 Nov 2015 02:30:28 GMT
+ Incoming O.S. Response +
-- State Machine Id: 168
HTTP/1.1 200 OK
Server: AkamaiGHost
Mime-Version: 1.0
Content-Type: video/abst
Content-Length: 122
Last-Modified: Thu, 05 Nov 2015 02:30:28 GMT
Expires: Thu, 05 Nov 2015 11:38:01 GMT
Cache-Control: max-age=0, no-cache
Pragma: no-cache
Date: Thu, 05 Nov 2015 11:38:01 GMT
Connection: keep-alive
Set-Cookie: _alid_=PmjLqgcUUqw6TP5gtK/xbg==;
path=/z/delayed/indvsa2015_INDVSSATEST1DAY1_1@336263/;
domain=sshds5-lh.akamaihd.net
+ Base Header for Building Response +
-- State Machine Id: 168
HTTP/1.1 200 OK
Server: AkamaiGHost
Mime-Version: 1.0
Content-Type: video/abst
Content-Length: 122
Last-Modified: Thu, 05 Nov 2015 02:30:28 GMT
Expires: Thu, 05 Nov 2015 11:38:01 GMT
Cache-Control: max-age=0, no-cache
Pragma: no-cache
Date: Thu, 05 Nov 2015 11:38:01 GMT
Connection: keep-alive
Set-Cookie: _alid_=PmjLqgcUUqw6TP5gtK/xbg==;
path=/z/delayed/indvsa2015_INDVSSATEST1DAY1_1@336263/;
domain=sshds5-lh.akamaihd.net
+ Proxy's Response 2 +
-- State Machine Id: 168
HTTP/1.1 304 Not Modified
Date: Thu, 05 Nov 2015 11:38:01 GMT
Expires: Thu, 05 Nov 2015 11:38:01 GMT
Cache-Control: max-age=0, no-cache
Connection: keep-alive
+ Proxy's Response (Client Conditionals) +
-- State
[jira] [Updated] (TS-3675) Make HTTP/2 upgrade contexts handle bad settings properly
[
https://issues.apache.org/jira/browse/TS-3675?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Leif Hedstrom updated TS-3675:
--
Fix Version/s: (was: 6.1.0)
sometime
> Make HTTP/2 upgrade contexts handle bad settings properly
> -
>
> Key: TS-3675
> URL: https://issues.apache.org/jira/browse/TS-3675
> Project: Traffic Server
> Issue Type: Bug
> Components: HTTP/2
>Reporter: Leif Hedstrom
> Fix For: sometime
>
>
> Right now, we have:
> {code}
> if (!http2_parse_settings_parameter(make_iovec(out_buf + nbytes,
> HTTP2_SETTINGS_PARAMETER_LEN), param) ||
>!http2_settings_parameter_is_valid(param)) {
> // TODO ignore incoming invalid parameters and send suitable
> SETTINGS frame.
> {code}
> And then we continue trying to set the "invalid" parameter anyways.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Commented] (TS-3612) Restructure Proxy Client Sessions to support transaction oriented Sessions execute transaction hooks and connection oriented Sessions execute session hooks
[ https://issues.apache.org/jira/browse/TS-3612?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14993295#comment-14993295 ] Bryan Call commented on TS-3612: Is there a design spec for this? > Restructure Proxy Client Sessions to support transaction oriented Sessions > execute transaction hooks and connection oriented Sessions execute session > hooks > --- > > Key: TS-3612 > URL: https://issues.apache.org/jira/browse/TS-3612 > Project: Traffic Server > Issue Type: Improvement > Components: HTTP, HTTP/2, SPDY >Reporter: Susan Hinrichs >Assignee: Alan M. Carroll > Fix For: sometime > > > In the current code, transaction and session hooks don't have access to H2 > and SPDY session data. This was partially addressed by TS-3578. > There was a discussion on the mailing list, and the consensus was that > session hooks should be invoked on session-oriented sessions (H2, SPDY, and > native HTTP/1.x) and transaction hooks should be invoked on > transaction-oriented sessions. > http://dev.trafficserver.apache.narkive.com/OX9XK0xn/spdy-h2-and-session-hooks -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (TS-3612) Restructure Proxy Client Sessions to support transaction oriented Sessions execute transaction hooks and connection oriented Sessions execute session hooks
[ https://issues.apache.org/jira/browse/TS-3612?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Leif Hedstrom updated TS-3612: -- Fix Version/s: (was: 6.1.0) sometime > Restructure Proxy Client Sessions to support transaction oriented Sessions > execute transaction hooks and connection oriented Sessions execute session > hooks > --- > > Key: TS-3612 > URL: https://issues.apache.org/jira/browse/TS-3612 > Project: Traffic Server > Issue Type: Improvement > Components: HTTP, HTTP/2, SPDY >Reporter: Susan Hinrichs >Assignee: Alan M. Carroll > Fix For: sometime > > > In the current code, transaction and session hooks don't have access to H2 > and SPDY session data. This was partially addressed by TS-3578. > There was a discussion on the mailing list, and the consensus was that > session hooks should be invoked on session-oriented sessions (H2, SPDY, and > native HTTP/1.x) and transaction hooks should be invoked on > transaction-oriented sessions. > http://dev.trafficserver.apache.narkive.com/OX9XK0xn/spdy-h2-and-session-hooks -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (TS-3584) SPDY and H2 requests should not trigger connection keep-alive processing
[ https://issues.apache.org/jira/browse/TS-3584?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14993288#comment-14993288 ] Leif Hedstrom commented on TS-3584: --- [~shinrich] Do we still want this, or just let it go? There's some work underway to (hopefully) eliminate use of FetchSM from H2 long term. > SPDY and H2 requests should not trigger connection keep-alive processing > > > Key: TS-3584 > URL: https://issues.apache.org/jira/browse/TS-3584 > Project: Traffic Server > Issue Type: Bug > Components: HTTP, HTTP/2, SPDY >Reporter: Susan Hinrichs >Assignee: Susan Hinrichs > Fix For: 6.1.0 > > > For HTTP 1.1 the default value for the Connection header is keep-alive. So > all requests coming from SPDY and H2 dutifully set up the HttpClientSession > for potential future reuse. > However, SPDY and H2 will create a new FetchSM request (and related > HttpClientSession) for every HTTP request, so the HttpClientSession will > never be reused. > This results in unnecessary complexity and inefficiency. I'm seeing some > crashes in SPDY start up that could be related to VC freeing race conditions. > I'd like to tidy this up to remove one element from the equation. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (TS-3584) SPDY and H2 requests should not trigger connection keep-alive processing
[ https://issues.apache.org/jira/browse/TS-3584?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14993290#comment-14993290 ] Bryan Call commented on TS-3584: I am not seeing any cores in production on this. Is this still an issue? > SPDY and H2 requests should not trigger connection keep-alive processing > > > Key: TS-3584 > URL: https://issues.apache.org/jira/browse/TS-3584 > Project: Traffic Server > Issue Type: Bug > Components: HTTP, HTTP/2, SPDY >Reporter: Susan Hinrichs >Assignee: Susan Hinrichs > Fix For: 6.1.0 > > > For HTTP 1.1 the default value for the Connection header is keep-alive. So > all requests coming from SPDY and H2 dutifully set up the HttpClientSession > for potential future reuse. > However, SPDY and H2 will create a new FetchSM request (and related > HttpClientSession) for every HTTP request, so the HttpClientSession will > never be reused. > This results in unnecessary complexity and inefficiency. I'm seeing some > crashes in SPDY start up that could be related to VC freeing race conditions. > I'd like to tidy this up to remove one element from the equation. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (TS-3535) Add priority feature to the HTTP/2 implementation
[ https://issues.apache.org/jira/browse/TS-3535?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14993284#comment-14993284 ] Masaori Koshiba commented on TS-3535: - I'll work for this > Add priority feature to the HTTP/2 implementation > - > > Key: TS-3535 > URL: https://issues.apache.org/jira/browse/TS-3535 > Project: Traffic Server > Issue Type: Improvement > Components: HTTP/2 >Reporter: Bryan Call > Fix For: 6.1.0 > > > Prioritizes the responses back to the client based on the priority level > specified by the HTTP/2 protocol. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (TS-3498) h2c (upgrade dance) seems to hang
[
https://issues.apache.org/jira/browse/TS-3498?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Leif Hedstrom updated TS-3498:
--
Fix Version/s: (was: 6.1.0)
sometime
> h2c (upgrade dance) seems to hang
> -
>
> Key: TS-3498
> URL: https://issues.apache.org/jira/browse/TS-3498
> Project: Traffic Server
> Issue Type: Bug
> Components: HTTP/2
>Reporter: Leif Hedstrom
>Assignee: Ryo Okubo
> Fix For: sometime
>
>
> I see
> {code}
> loki (09:37) 259/0 $ nghttp -v -u http://docs.trafficserver.apache.org
> [ 0.031] Connected
> [ 0.031] HTTP Upgrade request
> GET / HTTP/1.1
> Host: docs.trafficserver.apache.org
> Connection: Upgrade, HTTP2-Settings
> Upgrade: h2c-14
> HTTP2-Settings: AAMAAABkAAQAAP__
> Accept: */*
> User-Agent: nghttp2/0.7.4-DEV
> [ 0.066] HTTP Upgrade response
> HTTP/1.1 101 Switching Protocols
> Date: Sun, 05 Apr 2015 15:37:58 GMT
> Connection: Upgrade
> Via: http/1.1 ATS (ApacheTrafficServer/5.3.0 [c s f ])
> Server: ATS/5.3.0
> Upgrade: h2c-14
> [ 0.066] HTTP Upgrade success
> [ 0.066] recv SETTINGS frame
> (niv=6)
> [SETTINGS_HEADER_TABLE_SIZE(0x01):4096]
> [SETTINGS_ENABLE_PUSH(0x02):0]
> [SETTINGS_MAX_CONCURRENT_STREAMS(0x03):66]
> [SETTINGS_INITIAL_WINDOW_SIZE(0x04):123456]
> [SETTINGS_MAX_FRAME_SIZE(0x05):16384]
> [SETTINGS_MAX_HEADER_LIST_SIZE(0x06):4294967295]
> [ 0.066] send SETTINGS frame
> (niv=2)
> [SETTINGS_MAX_CONCURRENT_STREAMS(0x03):100]
> [SETTINGS_INITIAL_WINDOW_SIZE(0x04):65535]
> [ 0.066] send SETTINGS frame
> ; ACK
> (niv=0)
> [ 0.097] recv SETTINGS frame
> ; ACK
> (niv=0)
> {code}
> And then it hangs.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Created] (TS-3997) Disable h2c upgrades (for now)
Leif Hedstrom created TS-3997: - Summary: Disable h2c upgrades (for now) Key: TS-3997 URL: https://issues.apache.org/jira/browse/TS-3997 Project: Traffic Server Issue Type: Improvement Components: HTTP/2 Reporter: Bryan Call Fix For: 6.1.0 Prioritizes the responses back to the client based on the priority level specified by the HTTP/2 protocol. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Created] (TS-3998) Disable h2c upgrades (for now)
Leif Hedstrom created TS-3998:
-
Summary: Disable h2c upgrades (for now)
Key: TS-3998
URL: https://issues.apache.org/jira/browse/TS-3998
Project: Traffic Server
Issue Type: Bug
Components: HTTP/2
Reporter: Leif Hedstrom
Assignee: Ryo Okubo
Fix For: 6.1.0
I see
{code}
loki (09:37) 259/0 $ nghttp -v -u http://docs.trafficserver.apache.org
[ 0.031] Connected
[ 0.031] HTTP Upgrade request
GET / HTTP/1.1
Host: docs.trafficserver.apache.org
Connection: Upgrade, HTTP2-Settings
Upgrade: h2c-14
HTTP2-Settings: AAMAAABkAAQAAP__
Accept: */*
User-Agent: nghttp2/0.7.4-DEV
[ 0.066] HTTP Upgrade response
HTTP/1.1 101 Switching Protocols
Date: Sun, 05 Apr 2015 15:37:58 GMT
Connection: Upgrade
Via: http/1.1 ATS (ApacheTrafficServer/5.3.0 [c s f ])
Server: ATS/5.3.0
Upgrade: h2c-14
[ 0.066] HTTP Upgrade success
[ 0.066] recv SETTINGS frame
(niv=6)
[SETTINGS_HEADER_TABLE_SIZE(0x01):4096]
[SETTINGS_ENABLE_PUSH(0x02):0]
[SETTINGS_MAX_CONCURRENT_STREAMS(0x03):66]
[SETTINGS_INITIAL_WINDOW_SIZE(0x04):123456]
[SETTINGS_MAX_FRAME_SIZE(0x05):16384]
[SETTINGS_MAX_HEADER_LIST_SIZE(0x06):4294967295]
[ 0.066] send SETTINGS frame
(niv=2)
[SETTINGS_MAX_CONCURRENT_STREAMS(0x03):100]
[SETTINGS_INITIAL_WINDOW_SIZE(0x04):65535]
[ 0.066] send SETTINGS frame
; ACK
(niv=0)
[ 0.097] recv SETTINGS frame
; ACK
(niv=0)
{code}
And then it hangs.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Closed] (TS-3997) Disable h2c upgrades (for now)
[ https://issues.apache.org/jira/browse/TS-3997?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Leif Hedstrom closed TS-3997. - Resolution: Invalid > Disable h2c upgrades (for now) > -- > > Key: TS-3997 > URL: https://issues.apache.org/jira/browse/TS-3997 > Project: Traffic Server > Issue Type: Improvement > Components: HTTP/2 >Reporter: Bryan Call > Fix For: 6.1.0 > > > Prioritizes the responses back to the client based on the priority level > specified by the HTTP/2 protocol. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (TS-3485) We should honor ip_allow.config ACLs for HTTP/2 streams
[
https://issues.apache.org/jira/browse/TS-3485?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Leif Hedstrom updated TS-3485:
--
Summary: We should honor ip_allow.config ACLs for HTTP/2 streams (was: We
should honor ip_allow.config ACLs for HTTP/2 conns)
> We should honor ip_allow.config ACLs for HTTP/2 streams
> ---
>
> Key: TS-3485
> URL: https://issues.apache.org/jira/browse/TS-3485
> Project: Traffic Server
> Issue Type: Bug
> Components: HTTP/2
>Reporter: Leif Hedstrom
> Fix For: 6.1.0
>
>
> From the comments:
> {code}
> // XXX we need to refactor the ACL checks from HttpSessionAccept so that we
> can invoke them here, and also in
> // the SPDY protocol layer ...
> {code}
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Updated] (TS-3478) Indexing header representations on HPACK encoder
[ https://issues.apache.org/jira/browse/TS-3478?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Leif Hedstrom updated TS-3478: -- Assignee: Ryo Okubo (was: Leif Hedstrom) > Indexing header representations on HPACK encoder > > > Key: TS-3478 > URL: https://issues.apache.org/jira/browse/TS-3478 > Project: Traffic Server > Issue Type: Improvement > Components: HTTP/2 >Reporter: Ryo Okubo >Assignee: Ryo Okubo > Labels: review > Fix For: 6.1.0 > > Attachments: indexing.patch > > > Support other header field representations on HPACK encoder. > http://tools.ietf.org/html/draft-ietf-httpbis-header-compression-12#section-6 > Currently the encoder supports only [Literal Header Field never > Indexed|http://tools.ietf.org/html/draft-ietf-httpbis-header-compression-12#section-6.2.3]. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (TS-3996) CID 1338133: Control flow issues (DEADCODE) /cmd/traffic_manager/traffic_manager.cc
[
https://issues.apache.org/jira/browse/TS-3996?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Leif Hedstrom updated TS-3996:
--
Assignee: Alan M. Carroll
> CID 1338133: Control flow issues (DEADCODE)
> /cmd/traffic_manager/traffic_manager.cc
> -
>
> Key: TS-3996
> URL: https://issues.apache.org/jira/browse/TS-3996
> Project: Traffic Server
> Issue Type: Bug
> Components: Manager
>Reporter: Leif Hedstrom
>Assignee: Alan M. Carroll
> Fix For: 6.1.0
>
>
> {code}
> Hi,
> Please find the latest report on new defect(s) introduced to Apache Traffic
> Server found with Coverity Scan.
> 1 new defect(s) introduced to Apache Traffic Server found with Coverity Scan.
> 6 defect(s), reported by Coverity Scan earlier, were marked fixed in the
> recent build analyzed by Coverity Scan.
> New defect(s) Reported-by: Coverity Scan
> Showing 1 of 1 defect(s)
> ** CID 1338133: Control flow issues (DEADCODE)
> /cmd/traffic_manager/traffic_manager.cc: 569 in main()
>
> *** CID 1338133: Control flow issues (DEADCODE)
> /cmd/traffic_manager/traffic_manager.cc: 569 in main()
> 563 int facility_int;
> 564
> 565 facility_str = REC_readString(sys_var, &found);
> 566 ink_assert(found);
> 567
> 568 if (!found) {
>CID 1338133: Control flow issues (DEADCODE)
>Execution cannot reach this statement: "mgmt_elog(0, "Could not rea...".
> 569 mgmt_elog(0, "Could not read %s. Defaulting to LOG_DAEMON\n",
> sys_var);
> 570 facility_int = LOG_DAEMON;
> 571 } else {
> 572 facility_int = facility_string_to_int(facility_str);
> 573 ats_free(facility_str);
> 574 if (facility_int < 0) {
> {code}
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Updated] (TS-3996) CID 1338133: Control flow issues (DEADCODE) /cmd/traffic_manager/traffic_manager.cc
[
https://issues.apache.org/jira/browse/TS-3996?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Leif Hedstrom updated TS-3996:
--
Fix Version/s: 6.1.0
> CID 1338133: Control flow issues (DEADCODE)
> /cmd/traffic_manager/traffic_manager.cc
> -
>
> Key: TS-3996
> URL: https://issues.apache.org/jira/browse/TS-3996
> Project: Traffic Server
> Issue Type: Bug
> Components: Manager
>Reporter: Leif Hedstrom
> Fix For: 6.1.0
>
>
> {code}
> Hi,
> Please find the latest report on new defect(s) introduced to Apache Traffic
> Server found with Coverity Scan.
> 1 new defect(s) introduced to Apache Traffic Server found with Coverity Scan.
> 6 defect(s), reported by Coverity Scan earlier, were marked fixed in the
> recent build analyzed by Coverity Scan.
> New defect(s) Reported-by: Coverity Scan
> Showing 1 of 1 defect(s)
> ** CID 1338133: Control flow issues (DEADCODE)
> /cmd/traffic_manager/traffic_manager.cc: 569 in main()
>
> *** CID 1338133: Control flow issues (DEADCODE)
> /cmd/traffic_manager/traffic_manager.cc: 569 in main()
> 563 int facility_int;
> 564
> 565 facility_str = REC_readString(sys_var, &found);
> 566 ink_assert(found);
> 567
> 568 if (!found) {
>CID 1338133: Control flow issues (DEADCODE)
>Execution cannot reach this statement: "mgmt_elog(0, "Could not rea...".
> 569 mgmt_elog(0, "Could not read %s. Defaulting to LOG_DAEMON\n",
> sys_var);
> 570 facility_int = LOG_DAEMON;
> 571 } else {
> 572 facility_int = facility_string_to_int(facility_str);
> 573 ats_free(facility_str);
> 574 if (facility_int < 0) {
> {code}
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Created] (TS-3996) CID 1338133: Control flow issues (DEADCODE) /cmd/traffic_manager/traffic_manager.cc
Leif Hedstrom created TS-3996:
-
Summary: CID 1338133: Control flow issues (DEADCODE)
/cmd/traffic_manager/traffic_manager.cc
Key: TS-3996
URL: https://issues.apache.org/jira/browse/TS-3996
Project: Traffic Server
Issue Type: Bug
Components: Manager
Reporter: Leif Hedstrom
{code}
Hi,
Please find the latest report on new defect(s) introduced to Apache Traffic
Server found with Coverity Scan.
1 new defect(s) introduced to Apache Traffic Server found with Coverity Scan.
6 defect(s), reported by Coverity Scan earlier, were marked fixed in the recent
build analyzed by Coverity Scan.
New defect(s) Reported-by: Coverity Scan
Showing 1 of 1 defect(s)
** CID 1338133: Control flow issues (DEADCODE)
/cmd/traffic_manager/traffic_manager.cc: 569 in main()
*** CID 1338133: Control flow issues (DEADCODE)
/cmd/traffic_manager/traffic_manager.cc: 569 in main()
563 int facility_int;
564
565 facility_str = REC_readString(sys_var, &found);
566 ink_assert(found);
567
568 if (!found) {
CID 1338133: Control flow issues (DEADCODE)
Execution cannot reach this statement: "mgmt_elog(0, "Could not rea...".
569 mgmt_elog(0, "Could not read %s. Defaulting to LOG_DAEMON\n",
sys_var);
570 facility_int = LOG_DAEMON;
571 } else {
572 facility_int = facility_string_to_int(facility_str);
573 ats_free(facility_str);
574 if (facility_int < 0) {
{code}
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Commented] (TS-3991) Coredump seen on plugins written using CPP API
[
https://issues.apache.org/jira/browse/TS-3991?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14993016#comment-14993016
]
Brian Geffon commented on TS-3991:
--
Hi [~kichan] looks good to me! Wanna land it, or should I?
> Coredump seen on plugins written using CPP API
> --
>
> Key: TS-3991
> URL: https://issues.apache.org/jira/browse/TS-3991
> Project: Traffic Server
> Issue Type: Bug
> Components: CPP API, Plugins
>Reporter: Kit Chan
>Assignee: Brian Geffon
> Attachments: interceptplugin_crashfix.patch
>
>
> Here are the traces on the coredumps we are seeing
> #0 0x2aab682e99a0 in ?? ()
> No symbol table info available.
> #1 0x2b4b8179 in
> std::tr1::_Sp_counted_base<(__gnu_cxx::_Lock_policy)2>::_M_release
> (this=0x2aab6809cb10) at
> /usr/lib/gcc/x86_64-redhat-linux/4.4.7/../../../../include/c++/4.4.7/tr1_impl/boost_sp_counted_base.h:140
> No locals.
> #2 0x2b6dfb61 in
> std::tr1::__shared_count<(__gnu_cxx::_Lock_policy)2>::~__shared_count
> (this=0x2b1c832f8bc8, __in_chrg=) at
> /usr/lib/gcc/x86_64-redhat-linux/4.4.7/../../../../include/c++/4.4.7/tr1/shared_ptr.h:153
> No locals.
> #3 0x2b6df94e in std::tr1::__shared_ptr (__gnu_cxx::_Lock_policy)2>::~__shared_ptr (this=0x2b1c832f8bc0,
> __in_chrg=) at
> /usr/lib/gcc/x86_64-redhat-linux/4.4.7/../../../../include/c++/4.4.7/tr1/shared_ptr.h:358
> No locals.
> #4 0x2b6df98e in std::tr1::shared_ptr::~shared_ptr
> (this=0x2b1c832f8bc0, __in_chrg=) at
> /usr/lib/gcc/x86_64-redhat-linux/4.4.7/../../../../include/c++/4.4.7/tr1/shared_ptr.h:834
> No locals.
> #5 0x2b6f1e0a in
> atscppapi::ScopedSharedMutexTryLock::~ScopedSharedMutexTryLock
> (this=0x2b1c832f8bc0, __in_chrg=) at
> include/atscppapi/Mutex.h:234
> No locals.
> #6 0x2b6f1c77 in (anonymous namespace)::handleEvents
> (cont=0x28eb430, pristine_event=TS_EVENT_TIMEOUT,
> pristine_edata=0x2aab20079450) at InterceptPlugin.cc:347
> edata = 0x2aab20079450
> state = 0x2aab6809cb80
> __FUNCTION__ = "handleEvents"
> event = TS_EVENT_TIMEOUT
> scopedTryLock = { = {},
> mutex_ = std::tr1::shared_ptr (count 0) 0x2aab6809caa0, has_lock_ = false}
> #7 0x0050bac8 in INKContInternal::handle_event (this=0x28eb430,
> event=2, edata=0x2aab20079450) at InkAPI.cc:1000
> No locals.
> #8 0x004f70d8 in Continuation::handleEvent (this=0x28eb430, event=2,
> data=0x2aab20079450) at ../iocore/eventsystem/I_Continuation.h:146
> No locals.
> #9 0x0075a8d2 in EThread::process_event (this=0x2b1c80ed6010,
> e=0x2aab20079450, calling_code=2) at UnixEThread.cc:145
> c_temp = 0x28eb430
> lock = {m = {m_ptr = 0x2aaabc0eca50}, lock_acquired = true}
> #10 0x0075abed in EThread::execute (this=0x2b1c80ed6010) at
> UnixEThread.cc:224
> done_one = true
> e = 0x2aab20079450
> NegativeQueue = {> = {head = 0x257bcf0},
> tail = 0x257bcf0}
> next_time = 1444322819831472139
> #11 0x00759e50 in spawn_thread_internal (a=0x2447860) at Thread.cc:88
> p = 0x2447860
> #12 0x2b1c7f9cd9d1 in start_thread () from /lib64/libpthread.so.0
> No symbol table info available.
> #13 0x00381b8e88fd in clone () from /lib64/libc.so.6
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Updated] (TS-3123) Make proxy.config.http.transaction_active_timeout_in overridable
[ https://issues.apache.org/jira/browse/TS-3123?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Leif Hedstrom updated TS-3123: -- Labels: A (was: ) > Make proxy.config.http.transaction_active_timeout_in overridable > > > Key: TS-3123 > URL: https://issues.apache.org/jira/browse/TS-3123 > Project: Traffic Server > Issue Type: New Feature > Components: HTTP >Reporter: Leif Hedstrom >Assignee: Leif Hedstrom > Labels: A > Fix For: 6.1.0 > > > This also requires moving the setup to a slightly later state in the HttpSM. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Assigned] (TS-3123) Make proxy.config.http.transaction_active_timeout_in overridable
[ https://issues.apache.org/jira/browse/TS-3123?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Leif Hedstrom reassigned TS-3123: - Assignee: Leif Hedstrom (was: Mark Torluemke) > Make proxy.config.http.transaction_active_timeout_in overridable > > > Key: TS-3123 > URL: https://issues.apache.org/jira/browse/TS-3123 > Project: Traffic Server > Issue Type: New Feature > Components: HTTP >Reporter: Leif Hedstrom >Assignee: Leif Hedstrom > Fix For: 6.1.0 > > > This also requires moving the setup to a slightly later state in the HttpSM. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (TS-3991) Coredump seen on plugins written using CPP API
[
https://issues.apache.org/jira/browse/TS-3991?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14992821#comment-14992821
]
Kit Chan commented on TS-3991:
--
[~briang] , you have a chance to take a look at this?
> Coredump seen on plugins written using CPP API
> --
>
> Key: TS-3991
> URL: https://issues.apache.org/jira/browse/TS-3991
> Project: Traffic Server
> Issue Type: Bug
> Components: CPP API, Plugins
>Reporter: Kit Chan
>Assignee: Brian Geffon
> Attachments: interceptplugin_crashfix.patch
>
>
> Here are the traces on the coredumps we are seeing
> #0 0x2aab682e99a0 in ?? ()
> No symbol table info available.
> #1 0x2b4b8179 in
> std::tr1::_Sp_counted_base<(__gnu_cxx::_Lock_policy)2>::_M_release
> (this=0x2aab6809cb10) at
> /usr/lib/gcc/x86_64-redhat-linux/4.4.7/../../../../include/c++/4.4.7/tr1_impl/boost_sp_counted_base.h:140
> No locals.
> #2 0x2b6dfb61 in
> std::tr1::__shared_count<(__gnu_cxx::_Lock_policy)2>::~__shared_count
> (this=0x2b1c832f8bc8, __in_chrg=) at
> /usr/lib/gcc/x86_64-redhat-linux/4.4.7/../../../../include/c++/4.4.7/tr1/shared_ptr.h:153
> No locals.
> #3 0x2b6df94e in std::tr1::__shared_ptr (__gnu_cxx::_Lock_policy)2>::~__shared_ptr (this=0x2b1c832f8bc0,
> __in_chrg=) at
> /usr/lib/gcc/x86_64-redhat-linux/4.4.7/../../../../include/c++/4.4.7/tr1/shared_ptr.h:358
> No locals.
> #4 0x2b6df98e in std::tr1::shared_ptr::~shared_ptr
> (this=0x2b1c832f8bc0, __in_chrg=) at
> /usr/lib/gcc/x86_64-redhat-linux/4.4.7/../../../../include/c++/4.4.7/tr1/shared_ptr.h:834
> No locals.
> #5 0x2b6f1e0a in
> atscppapi::ScopedSharedMutexTryLock::~ScopedSharedMutexTryLock
> (this=0x2b1c832f8bc0, __in_chrg=) at
> include/atscppapi/Mutex.h:234
> No locals.
> #6 0x2b6f1c77 in (anonymous namespace)::handleEvents
> (cont=0x28eb430, pristine_event=TS_EVENT_TIMEOUT,
> pristine_edata=0x2aab20079450) at InterceptPlugin.cc:347
> edata = 0x2aab20079450
> state = 0x2aab6809cb80
> __FUNCTION__ = "handleEvents"
> event = TS_EVENT_TIMEOUT
> scopedTryLock = { = {},
> mutex_ = std::tr1::shared_ptr (count 0) 0x2aab6809caa0, has_lock_ = false}
> #7 0x0050bac8 in INKContInternal::handle_event (this=0x28eb430,
> event=2, edata=0x2aab20079450) at InkAPI.cc:1000
> No locals.
> #8 0x004f70d8 in Continuation::handleEvent (this=0x28eb430, event=2,
> data=0x2aab20079450) at ../iocore/eventsystem/I_Continuation.h:146
> No locals.
> #9 0x0075a8d2 in EThread::process_event (this=0x2b1c80ed6010,
> e=0x2aab20079450, calling_code=2) at UnixEThread.cc:145
> c_temp = 0x28eb430
> lock = {m = {m_ptr = 0x2aaabc0eca50}, lock_acquired = true}
> #10 0x0075abed in EThread::execute (this=0x2b1c80ed6010) at
> UnixEThread.cc:224
> done_one = true
> e = 0x2aab20079450
> NegativeQueue = {> = {head = 0x257bcf0},
> tail = 0x257bcf0}
> next_time = 1444322819831472139
> #11 0x00759e50 in spawn_thread_internal (a=0x2447860) at Thread.cc:88
> p = 0x2447860
> #12 0x2b1c7f9cd9d1 in start_thread () from /lib64/libpthread.so.0
> No symbol table info available.
> #13 0x00381b8e88fd in clone () from /lib64/libc.so.6
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Commented] (TS-3994) Internal Redirect follow should allow to use API set cache key.
[ https://issues.apache.org/jira/browse/TS-3994?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14992253#comment-14992253 ] ASF subversion and git services commented on TS-3994: - Commit 4ab20913baad1fffd1c6f02ff9f3fbbc86cff7b9 in trafficserver's branch refs/heads/master from [~sudheerv] [ https://git-wip-us.apache.org/repos/asf?p=trafficserver.git;h=4ab2091 ] [TS-3994] update docs > Internal Redirect follow should allow to use API set cache key. > --- > > Key: TS-3994 > URL: https://issues.apache.org/jira/browse/TS-3994 > Project: Traffic Server > Issue Type: Improvement > Components: HTTP >Reporter: Sudheer Vinukonda >Assignee: Sudheer Vinukonda > > Currently, during redirect follow, uses the Location header in the 3xx > response as the cache key (and does not use the cache key set by using an > API, for example). > This can break the ability to serve cached response in some cases, where the > redirect follow is performed (via a plugin to implement a simple fail-over > mechanism between origin hosts, for example). > Opening this jira to add a new configuration option to allow using original > request cache key to lookup during redirect follow. > This was briefly discussed in TS-3652, but, TS-3652 was actually tracking a > different problem (turned out to be a regression) that prevents a redirect > response being cached altogether. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (TS-3994) Internal Redirect follow should allow to use API set cache key.
[ https://issues.apache.org/jira/browse/TS-3994?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14992247#comment-14992247 ] ASF subversion and git services commented on TS-3994: - Commit f2ba1dc71cd68bf7a98c87a3e1f19b131899847f in trafficserver's branch refs/heads/master from [~sudheerv] [ https://git-wip-us.apache.org/repos/asf?p=trafficserver.git;h=f2ba1dc ] [TS-3994] Configurable option to allow redirect follow to use original request cache key. > Internal Redirect follow should allow to use API set cache key. > --- > > Key: TS-3994 > URL: https://issues.apache.org/jira/browse/TS-3994 > Project: Traffic Server > Issue Type: Improvement > Components: HTTP >Reporter: Sudheer Vinukonda >Assignee: Sudheer Vinukonda > > Currently, during redirect follow, uses the Location header in the 3xx > response as the cache key (and does not use the cache key set by using an > API, for example). > This can break the ability to serve cached response in some cases, where the > redirect follow is performed (via a plugin to implement a simple fail-over > mechanism between origin hosts, for example). > Opening this jira to add a new configuration option to allow using original > request cache key to lookup during redirect follow. > This was briefly discussed in TS-3652, but, TS-3652 was actually tracking a > different problem (turned out to be a regression) that prevents a redirect > response being cached altogether. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (TS-3994) Internal Redirect follow should allow to use API set cache key.
[ https://issues.apache.org/jira/browse/TS-3994?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Sudheer Vinukonda updated TS-3994: -- Description: Currently, during redirect follow, uses the Location header in the 3xx response as the cache key (and does not use the cache key set by using an API, for example). This can break the ability to serve cached response in some cases, where the redirect follow is performed (via a plugin to implement a simple fail-over mechanism between origin hosts, for example). Opening this jira to add a new configuration option to allow using original request cache key to lookup during redirect follow. This was briefly discussed in TS-3652, but, TS-3652 was actually tracking a different problem (turned out to be a regression) that prevents a redirect response being cached altogether. was: Currently, during redirect follow, the cache key set by using an API for example. This breaks the ability to serve cached response in some cases, where the redirect follow is performed via a plugin. Opening this jira to add a new configuration option to allow using original request cache key to lookup during redirect follow. > Internal Redirect follow should allow to use API set cache key. > --- > > Key: TS-3994 > URL: https://issues.apache.org/jira/browse/TS-3994 > Project: Traffic Server > Issue Type: Improvement > Components: HTTP >Reporter: Sudheer Vinukonda >Assignee: Sudheer Vinukonda > > Currently, during redirect follow, uses the Location header in the 3xx > response as the cache key (and does not use the cache key set by using an > API, for example). > This can break the ability to serve cached response in some cases, where the > redirect follow is performed (via a plugin to implement a simple fail-over > mechanism between origin hosts, for example). > Opening this jira to add a new configuration option to allow using original > request cache key to lookup during redirect follow. > This was briefly discussed in TS-3652, but, TS-3652 was actually tracking a > different problem (turned out to be a regression) that prevents a redirect > response being cached altogether. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (TS-306) enable log rotation for diags.log
[ https://issues.apache.org/jira/browse/TS-306?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14991839#comment-14991839 ] ASF subversion and git services commented on TS-306: Commit 53d4854434a2ab4cab26adfe6af2a1ef01bae224 in trafficserver's branch refs/heads/master from [~amc] [ https://git-wip-us.apache.org/repos/asf?p=trafficserver.git;h=53d4854 ] TS-306: Fix clang warning, ambiguous constructor use. > enable log rotation for diags.log > - > > Key: TS-306 > URL: https://issues.apache.org/jira/browse/TS-306 > Project: Traffic Server > Issue Type: Improvement > Components: Logging >Reporter: Miles Libbey >Assignee: Daniel Xu > Labels: newbie > Fix For: 6.1.0 > > > (from yahoo bug 913896) > Original description > by Leif Hedstrom 3 years ago at 2006-12-04 12:42 > There might be reasons why this file might get filled up, e.g. libraries used > by plugins producing output on STDOUT/STDERR. A few suggestions have been > made, to somehow rotate traffic.out. One possible solution (suggested by > Ryan) is to use cronolog (http://cronolog.org/), which seems like a fine idea. > > > Comment 1 > by Joseph Rothrock 2 years ago at 2007-10-17 09:13:24 > Maybe consider rolling diags.log as well. -Feature enhancement. > > Comment 2 > by Kevin Dalley 13 months ago at 2009-03-04 15:32:18 > When traffic.out gets filled up, error.log stops filing up, even though > rotation is turned on. This is > counter-intuitive. Rotation does not control traffic.out, but a large > traffic.out will stop error.log from being > written. > -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (TS-3995) "[hcoofsr] conditional request, 200 response, send back 304 if possible [crc=304]" breaks akamaihd.net live streaming
[
https://issues.apache.org/jira/browse/TS-3995?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14991701#comment-14991701
]
Nikolai Gorchilov commented on TS-3995:
---
I did a temporary fix that seems to resolve the issue, but not exactly sure
what else it breaks:
{noformat}
--- trafficserver-5.3.2/proxy/http/HttpTransact.cc 2015-11-05
15:23:42.0 +0200
+++ trafficserver-5.3.2/proxy/http/HttpTransact.cc 2015-11-05
15:25:16.0 +0200
@@ -4330,8 +4330,9 @@ HttpTransact::handle_cache_operation_on_
resp->set_expires(exp_time);
}
} else if (is_request_conditional(&s->hdr_info.client_request) &&
server_response_code == HTTP_STATUS_OK) {
-client_response_code =
-
HttpTransactCache::match_response_to_request_conditionals(&s->hdr_info.client_request,
&s->hdr_info.server_response);
+client_response_code = (s->txn_conf->cache_when_to_revalidate != 4)
+ ?
HttpTransactCache::match_response_to_request_conditionals(&s->hdr_info.client_request,
&s->hdr_info.server_response)
+ : server_response_code;
DebugTxn("http_trans", "[hcoofsr] conditional request, 200 "
"response, send back 304 if possible [crc=%d]",
{noformat}
> "[hcoofsr] conditional request, 200 response, send back 304 if possible
> [crc=304]" breaks akamaihd.net live streaming
> -
>
> Key: TS-3995
> URL: https://issues.apache.org/jira/browse/TS-3995
> Project: Traffic Server
> Issue Type: Bug
> Components: Cache, Core, HTTP
>Affects Versions: 5.3.2
>Reporter: Nikolai Gorchilov
>
> Caching proxy running ATS 5.3.x (5.3.0, 5.3.1, 5.3.2 all fail) with
> proxy.config.http.cache.when_to_revalidate = 4 breaks akamaihd.net live
> streaming by overwriting non-cacheable origin response from 200 to 304
> received against conditional request originating from the client.
> Here's a log of all request and response headers for a single transaction,
> collected via debug:
> {noformat}
> + Incoming Request +
> -- State Machine Id: 168
> GET
> http:///z/delayed/indvsa2015_INDVSSATEST1DAY1_1@336263/464_209823ecd2922291-p.bootstrap?g=YCEAMIWDQZQT&hdntl=exp=1446809835~acl=%2f*~data=hdntl~hmac=ebaedb13781605ce7f9f26b84e1346a7d43ecf0dfcc99e6b53e32487565ba3f8&hdcore=3.7.0&plugin=aasp-3.7.0.39.44
> HTTP/1.1
> Host: sshds5-lh.akamaihd.net
> Connection: keep-alive
> User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10_11_1)
> AppleWebKit/537.36 (KHTML, like Gecko) Chrome/46.0.2490.80 Safari/537.36
> X-Requested-With: ShockwaveFlash/19.0.0.226
> Accept: */*
> DNT: 1
> Referer: http://www.hotstar.com/
> Accept-Encoding: gzip
> Accept-Language: en-US,en;q=0.8,bg;q=0.6
> Cookie: _alid_=PmjLqgcUUqw6TP5gtK/xbg==;
> hdntl=exp=1446809835~acl=%2f*~data=hdntl~hmac=ebaedb13781605ce7f9f26b84e1346a7d43ecf0dfcc99e6b53e32487565ba3f8
> If-Modified-Since: Thu, 05 Nov 2015 02:30:28 GMT
> + Proxy's Request +
> -- State Machine Id: 168
> GET
> /z/delayed/indvsa2015_INDVSSATEST1DAY1_1@336263/464_209823ecd2922291-p.bootstrap?g=YCEAMIWDQZQT&hdntl=exp=1446809835~acl=%2f*~data=hdntl~hmac=ebaedb13781605ce7f9f26b84e1346a7d43ecf0dfcc99e6b53e32487565ba3f8&hdcore=3.7.0&plugin=aasp-3.7.0.39.44
> HTTP/1.1
> Host: sshds5-lh.akamaihd.net
> User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10_11_1)
> AppleWebKit/537.36 (KHTML, like Gecko) Chrome/46.0.2490.80 Safari/537.36
> X-Requested-With: ShockwaveFlash/19.0.0.226
> Accept: */*
> DNT: 1
> Referer: http://www.hotstar.com/
> Accept-Encoding: gzip
> Accept-Language: en-US,en;q=0.8,bg;q=0.6
> Cookie: _alid_=PmjLqgcUUqw6TP5gtK/xbg==;
> hdntl=exp=1446809835~acl=%2f*~data=hdntl~hmac=ebaedb13781605ce7f9f26b84e1346a7d43ecf0dfcc99e6b53e32487565ba3f8
> If-Modified-Since: Thu, 05 Nov 2015 02:30:28 GMT
> + Proxy's Request after hooks +
> -- State Machine Id: 168
> GET
> /z/delayed/indvsa2015_INDVSSATEST1DAY1_1@336263/464_209823ecd2922291-p.bootstrap?g=YCEAMIWDQZQT&hdntl=exp=1446809835~acl=%2f*~data=hdntl~hmac=ebaedb13781605ce7f9f26b84e1346a7d43ecf0dfcc99e6b53e32487565ba3f8&hdcore=3.7.0&plugin=aasp-3.7.0.39.44
> HTTP/1.1
> Host: sshds5-lh.akamaihd.net
> User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10_11_1)
> AppleWebKit/537.36 (KHTML, like Gecko) Chrome/46.0.2490.80 Safari/537.36
> X-Requested-With: ShockwaveFlash/19.0.0.226
> Accept: */*
> DNT: 1
> Referer: http://www.hotstar.com/
> Accept-Encoding: gzip
> Accept-Language: en-US,en;q=0.8,bg;q=0.6
> Cookie: _alid_=PmjLqgcUUqw6TP5gtK/xbg==;
> hdntl=exp=1446809835~acl=%2f*~data=hdntl~hmac=ebaedb13781605ce7f9f26b84e1346a7d43ecf0dfcc99e6b53e32487565ba3f8
> If-Modified-Since: Thu, 05 Nov 2015 02:30:28 GMT
> + Incoming O.S. Response +
[jira] [Updated] (TS-3995) "[hcoofsr] conditional request, 200 response, send back 304 if possible [crc=304]" breaks akamaihd.net live streaming
[
https://issues.apache.org/jira/browse/TS-3995?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Nikolai Gorchilov updated TS-3995:
--
Description:
Caching proxy running ATS 5.3.x (5.3.0, 5.3.1, 5.3.2 all fail) with
proxy.config.http.cache.when_to_revalidate = 4 breaks akamaihd.net live
streaming by overwriting non-cacheable origin response from 200 to 304 received
against conditional request originating from the client.
Here's a log of all request and response headers for a single transaction,
collected via debug:
{noformat}
+ Incoming Request +
-- State Machine Id: 168
GET
http:///z/delayed/indvsa2015_INDVSSATEST1DAY1_1@336263/464_209823ecd2922291-p.bootstrap?g=YCEAMIWDQZQT&hdntl=exp=1446809835~acl=%2f*~data=hdntl~hmac=ebaedb13781605ce7f9f26b84e1346a7d43ecf0dfcc99e6b53e32487565ba3f8&hdcore=3.7.0&plugin=aasp-3.7.0.39.44
HTTP/1.1
Host: sshds5-lh.akamaihd.net
Connection: keep-alive
User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10_11_1) AppleWebKit/537.36
(KHTML, like Gecko) Chrome/46.0.2490.80 Safari/537.36
X-Requested-With: ShockwaveFlash/19.0.0.226
Accept: */*
DNT: 1
Referer: http://www.hotstar.com/
Accept-Encoding: gzip
Accept-Language: en-US,en;q=0.8,bg;q=0.6
Cookie: _alid_=PmjLqgcUUqw6TP5gtK/xbg==;
hdntl=exp=1446809835~acl=%2f*~data=hdntl~hmac=ebaedb13781605ce7f9f26b84e1346a7d43ecf0dfcc99e6b53e32487565ba3f8
If-Modified-Since: Thu, 05 Nov 2015 02:30:28 GMT
+ Proxy's Request +
-- State Machine Id: 168
GET
/z/delayed/indvsa2015_INDVSSATEST1DAY1_1@336263/464_209823ecd2922291-p.bootstrap?g=YCEAMIWDQZQT&hdntl=exp=1446809835~acl=%2f*~data=hdntl~hmac=ebaedb13781605ce7f9f26b84e1346a7d43ecf0dfcc99e6b53e32487565ba3f8&hdcore=3.7.0&plugin=aasp-3.7.0.39.44
HTTP/1.1
Host: sshds5-lh.akamaihd.net
User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10_11_1) AppleWebKit/537.36
(KHTML, like Gecko) Chrome/46.0.2490.80 Safari/537.36
X-Requested-With: ShockwaveFlash/19.0.0.226
Accept: */*
DNT: 1
Referer: http://www.hotstar.com/
Accept-Encoding: gzip
Accept-Language: en-US,en;q=0.8,bg;q=0.6
Cookie: _alid_=PmjLqgcUUqw6TP5gtK/xbg==;
hdntl=exp=1446809835~acl=%2f*~data=hdntl~hmac=ebaedb13781605ce7f9f26b84e1346a7d43ecf0dfcc99e6b53e32487565ba3f8
If-Modified-Since: Thu, 05 Nov 2015 02:30:28 GMT
+ Proxy's Request after hooks +
-- State Machine Id: 168
GET
/z/delayed/indvsa2015_INDVSSATEST1DAY1_1@336263/464_209823ecd2922291-p.bootstrap?g=YCEAMIWDQZQT&hdntl=exp=1446809835~acl=%2f*~data=hdntl~hmac=ebaedb13781605ce7f9f26b84e1346a7d43ecf0dfcc99e6b53e32487565ba3f8&hdcore=3.7.0&plugin=aasp-3.7.0.39.44
HTTP/1.1
Host: sshds5-lh.akamaihd.net
User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10_11_1) AppleWebKit/537.36
(KHTML, like Gecko) Chrome/46.0.2490.80 Safari/537.36
X-Requested-With: ShockwaveFlash/19.0.0.226
Accept: */*
DNT: 1
Referer: http://www.hotstar.com/
Accept-Encoding: gzip
Accept-Language: en-US,en;q=0.8,bg;q=0.6
Cookie: _alid_=PmjLqgcUUqw6TP5gtK/xbg==;
hdntl=exp=1446809835~acl=%2f*~data=hdntl~hmac=ebaedb13781605ce7f9f26b84e1346a7d43ecf0dfcc99e6b53e32487565ba3f8
If-Modified-Since: Thu, 05 Nov 2015 02:30:28 GMT
+ Incoming O.S. Response +
-- State Machine Id: 168
HTTP/1.1 200 OK
Server: AkamaiGHost
Mime-Version: 1.0
Content-Type: video/abst
Content-Length: 122
Last-Modified: Thu, 05 Nov 2015 02:30:28 GMT
Expires: Thu, 05 Nov 2015 11:38:01 GMT
Cache-Control: max-age=0, no-cache
Pragma: no-cache
Date: Thu, 05 Nov 2015 11:38:01 GMT
Connection: keep-alive
Set-Cookie: _alid_=PmjLqgcUUqw6TP5gtK/xbg==;
path=/z/delayed/indvsa2015_INDVSSATEST1DAY1_1@336263/;
domain=sshds5-lh.akamaihd.net
+ Base Header for Building Response +
-- State Machine Id: 168
HTTP/1.1 200 OK
Server: AkamaiGHost
Mime-Version: 1.0
Content-Type: video/abst
Content-Length: 122
Last-Modified: Thu, 05 Nov 2015 02:30:28 GMT
Expires: Thu, 05 Nov 2015 11:38:01 GMT
Cache-Control: max-age=0, no-cache
Pragma: no-cache
Date: Thu, 05 Nov 2015 11:38:01 GMT
Connection: keep-alive
Set-Cookie: _alid_=PmjLqgcUUqw6TP5gtK/xbg==;
path=/z/delayed/indvsa2015_INDVSSATEST1DAY1_1@336263/;
domain=sshds5-lh.akamaihd.net
+ Proxy's Response 2 +
-- State Machine Id: 168
HTTP/1.1 304 Not Modified
Date: Thu, 05 Nov 2015 11:38:01 GMT
Expires: Thu, 05 Nov 2015 11:38:01 GMT
Cache-Control: max-age=0, no-cache
Connection: keep-alive
+ Proxy's Response (Client Conditionals) +
-- State Machine Id: 168
HTTP/1.1 304 Not Modified
Date: Thu, 05 Nov 2015 11:38:01 GMT
Expires: Thu, 05 Nov 2015 11:38:01 GMT
Cache-Control: max-age=0, no-cache
Connection: keep-alive
{noformat}
was:
Caching proxy running ATS 5.3.x (5.3.0, 5.3.1, 5.3.2 all fail) with
proxy.config.http.cache.when_to_revalidate = 4 breaks akamaihd.net live
streaming by overwriting non-cacheable origin response from 200 to 304 to a
client conditional request.
Here's a log of all request and response headers for a single transaction,
collec
[jira] [Created] (TS-3995) "[hcoofsr] conditional request, 200 response, send back 304 if possible [crc=304]" breaks akamaihd.net live streaming
Nikolai Gorchilov created TS-3995:
-
Summary: "[hcoofsr] conditional request, 200 response, send back
304 if possible [crc=304]" breaks akamaihd.net live streaming
Key: TS-3995
URL: https://issues.apache.org/jira/browse/TS-3995
Project: Traffic Server
Issue Type: Bug
Components: Cache, Core, HTTP
Reporter: Nikolai Gorchilov
Caching proxy running ATS 5.3.x (5.3.0, 5.3.1, 5.3.2 all fail) with
proxy.config.http.cache.when_to_revalidate = 4 breaks akamaihd.net live
streaming by overwriting non-cacheable origin response from 200 to 304 to a
client conditional request.
Here's a log of all request and response headers for a single transaction,
collected via debug:
{noformat}
+ Incoming Request +
-- State Machine Id: 168
GET
http:///z/delayed/indvsa2015_INDVSSATEST1DAY1_1@336263/464_209823ecd2922291-p.bootstrap?g=YCEAMIWDQZQT&hdntl=exp=1446809835~acl=%2f*~data=hdntl~hmac=ebaedb13781605ce7f9f26b84e1346a7d43ecf0dfcc99e6b53e32487565ba3f8&hdcore=3.7.0&plugin=aasp-3.7.0.39.44
HTTP/1.1
Host: sshds5-lh.akamaihd.net
Connection: keep-alive
User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10_11_1) AppleWebKit/537.36
(KHTML, like Gecko) Chrome/46.0.2490.80 Safari/537.36
X-Requested-With: ShockwaveFlash/19.0.0.226
Accept: */*
DNT: 1
Referer: http://www.hotstar.com/
Accept-Encoding: gzip
Accept-Language: en-US,en;q=0.8,bg;q=0.6
Cookie: _alid_=PmjLqgcUUqw6TP5gtK/xbg==;
hdntl=exp=1446809835~acl=%2f*~data=hdntl~hmac=ebaedb13781605ce7f9f26b84e1346a7d43ecf0dfcc99e6b53e32487565ba3f8
If-Modified-Since: Thu, 05 Nov 2015 02:30:28 GMT
+ Proxy's Request +
-- State Machine Id: 168
GET
/z/delayed/indvsa2015_INDVSSATEST1DAY1_1@336263/464_209823ecd2922291-p.bootstrap?g=YCEAMIWDQZQT&hdntl=exp=1446809835~acl=%2f*~data=hdntl~hmac=ebaedb13781605ce7f9f26b84e1346a7d43ecf0dfcc99e6b53e32487565ba3f8&hdcore=3.7.0&plugin=aasp-3.7.0.39.44
HTTP/1.1
Host: sshds5-lh.akamaihd.net
User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10_11_1) AppleWebKit/537.36
(KHTML, like Gecko) Chrome/46.0.2490.80 Safari/537.36
X-Requested-With: ShockwaveFlash/19.0.0.226
Accept: */*
DNT: 1
Referer: http://www.hotstar.com/
Accept-Encoding: gzip
Accept-Language: en-US,en;q=0.8,bg;q=0.6
Cookie: _alid_=PmjLqgcUUqw6TP5gtK/xbg==;
hdntl=exp=1446809835~acl=%2f*~data=hdntl~hmac=ebaedb13781605ce7f9f26b84e1346a7d43ecf0dfcc99e6b53e32487565ba3f8
If-Modified-Since: Thu, 05 Nov 2015 02:30:28 GMT
+ Proxy's Request after hooks +
-- State Machine Id: 168
GET
/z/delayed/indvsa2015_INDVSSATEST1DAY1_1@336263/464_209823ecd2922291-p.bootstrap?g=YCEAMIWDQZQT&hdntl=exp=1446809835~acl=%2f*~data=hdntl~hmac=ebaedb13781605ce7f9f26b84e1346a7d43ecf0dfcc99e6b53e32487565ba3f8&hdcore=3.7.0&plugin=aasp-3.7.0.39.44
HTTP/1.1
Host: sshds5-lh.akamaihd.net
User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10_11_1) AppleWebKit/537.36
(KHTML, like Gecko) Chrome/46.0.2490.80 Safari/537.36
X-Requested-With: ShockwaveFlash/19.0.0.226
Accept: */*
DNT: 1
Referer: http://www.hotstar.com/
Accept-Encoding: gzip
Accept-Language: en-US,en;q=0.8,bg;q=0.6
Cookie: _alid_=PmjLqgcUUqw6TP5gtK/xbg==;
hdntl=exp=1446809835~acl=%2f*~data=hdntl~hmac=ebaedb13781605ce7f9f26b84e1346a7d43ecf0dfcc99e6b53e32487565ba3f8
If-Modified-Since: Thu, 05 Nov 2015 02:30:28 GMT
+ Incoming O.S. Response +
-- State Machine Id: 168
HTTP/1.1 200 OK
Server: AkamaiGHost
Mime-Version: 1.0
Content-Type: video/abst
Content-Length: 122
Last-Modified: Thu, 05 Nov 2015 02:30:28 GMT
Expires: Thu, 05 Nov 2015 11:38:01 GMT
Cache-Control: max-age=0, no-cache
Pragma: no-cache
Date: Thu, 05 Nov 2015 11:38:01 GMT
Connection: keep-alive
Set-Cookie: _alid_=PmjLqgcUUqw6TP5gtK/xbg==;
path=/z/delayed/indvsa2015_INDVSSATEST1DAY1_1@336263/;
domain=sshds5-lh.akamaihd.net
+ Base Header for Building Response +
-- State Machine Id: 168
HTTP/1.1 200 OK
Server: AkamaiGHost
Mime-Version: 1.0
Content-Type: video/abst
Content-Length: 122
Last-Modified: Thu, 05 Nov 2015 02:30:28 GMT
Expires: Thu, 05 Nov 2015 11:38:01 GMT
Cache-Control: max-age=0, no-cache
Pragma: no-cache
Date: Thu, 05 Nov 2015 11:38:01 GMT
Connection: keep-alive
Set-Cookie: _alid_=PmjLqgcUUqw6TP5gtK/xbg==;
path=/z/delayed/indvsa2015_INDVSSATEST1DAY1_1@336263/;
domain=sshds5-lh.akamaihd.net
+ Proxy's Response 2 +
-- State Machine Id: 168
HTTP/1.1 304 Not Modified
Date: Thu, 05 Nov 2015 11:38:01 GMT
Expires: Thu, 05 Nov 2015 11:38:01 GMT
Cache-Control: max-age=0, no-cache
Connection: keep-alive
+ Proxy's Response (Client Conditionals) +
-- State Machine Id: 168
HTTP/1.1 304 Not Modified
Date: Thu, 05 Nov 2015 11:38:01 GMT
Expires: Thu, 05 Nov 2015 11:38:01 GMT
Cache-Control: max-age=0, no-cache
Connection: keep-alive
{noformat}
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Updated] (TS-3995) "[hcoofsr] conditional request, 200 response, send back 304 if possible [crc=304]" breaks akamaihd.net live streaming
[
https://issues.apache.org/jira/browse/TS-3995?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Nikolai Gorchilov updated TS-3995:
--
Affects Version/s: 5.3.2
> "[hcoofsr] conditional request, 200 response, send back 304 if possible
> [crc=304]" breaks akamaihd.net live streaming
> -
>
> Key: TS-3995
> URL: https://issues.apache.org/jira/browse/TS-3995
> Project: Traffic Server
> Issue Type: Bug
> Components: Cache, Core, HTTP
>Affects Versions: 5.3.2
>Reporter: Nikolai Gorchilov
>
> Caching proxy running ATS 5.3.x (5.3.0, 5.3.1, 5.3.2 all fail) with
> proxy.config.http.cache.when_to_revalidate = 4 breaks akamaihd.net live
> streaming by overwriting non-cacheable origin response from 200 to 304 to a
> client conditional request.
> Here's a log of all request and response headers for a single transaction,
> collected via debug:
> {noformat}
> + Incoming Request +
> -- State Machine Id: 168
> GET
> http:///z/delayed/indvsa2015_INDVSSATEST1DAY1_1@336263/464_209823ecd2922291-p.bootstrap?g=YCEAMIWDQZQT&hdntl=exp=1446809835~acl=%2f*~data=hdntl~hmac=ebaedb13781605ce7f9f26b84e1346a7d43ecf0dfcc99e6b53e32487565ba3f8&hdcore=3.7.0&plugin=aasp-3.7.0.39.44
> HTTP/1.1
> Host: sshds5-lh.akamaihd.net
> Connection: keep-alive
> User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10_11_1)
> AppleWebKit/537.36 (KHTML, like Gecko) Chrome/46.0.2490.80 Safari/537.36
> X-Requested-With: ShockwaveFlash/19.0.0.226
> Accept: */*
> DNT: 1
> Referer: http://www.hotstar.com/
> Accept-Encoding: gzip
> Accept-Language: en-US,en;q=0.8,bg;q=0.6
> Cookie: _alid_=PmjLqgcUUqw6TP5gtK/xbg==;
> hdntl=exp=1446809835~acl=%2f*~data=hdntl~hmac=ebaedb13781605ce7f9f26b84e1346a7d43ecf0dfcc99e6b53e32487565ba3f8
> If-Modified-Since: Thu, 05 Nov 2015 02:30:28 GMT
> + Proxy's Request +
> -- State Machine Id: 168
> GET
> /z/delayed/indvsa2015_INDVSSATEST1DAY1_1@336263/464_209823ecd2922291-p.bootstrap?g=YCEAMIWDQZQT&hdntl=exp=1446809835~acl=%2f*~data=hdntl~hmac=ebaedb13781605ce7f9f26b84e1346a7d43ecf0dfcc99e6b53e32487565ba3f8&hdcore=3.7.0&plugin=aasp-3.7.0.39.44
> HTTP/1.1
> Host: sshds5-lh.akamaihd.net
> User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10_11_1)
> AppleWebKit/537.36 (KHTML, like Gecko) Chrome/46.0.2490.80 Safari/537.36
> X-Requested-With: ShockwaveFlash/19.0.0.226
> Accept: */*
> DNT: 1
> Referer: http://www.hotstar.com/
> Accept-Encoding: gzip
> Accept-Language: en-US,en;q=0.8,bg;q=0.6
> Cookie: _alid_=PmjLqgcUUqw6TP5gtK/xbg==;
> hdntl=exp=1446809835~acl=%2f*~data=hdntl~hmac=ebaedb13781605ce7f9f26b84e1346a7d43ecf0dfcc99e6b53e32487565ba3f8
> If-Modified-Since: Thu, 05 Nov 2015 02:30:28 GMT
> + Proxy's Request after hooks +
> -- State Machine Id: 168
> GET
> /z/delayed/indvsa2015_INDVSSATEST1DAY1_1@336263/464_209823ecd2922291-p.bootstrap?g=YCEAMIWDQZQT&hdntl=exp=1446809835~acl=%2f*~data=hdntl~hmac=ebaedb13781605ce7f9f26b84e1346a7d43ecf0dfcc99e6b53e32487565ba3f8&hdcore=3.7.0&plugin=aasp-3.7.0.39.44
> HTTP/1.1
> Host: sshds5-lh.akamaihd.net
> User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10_11_1)
> AppleWebKit/537.36 (KHTML, like Gecko) Chrome/46.0.2490.80 Safari/537.36
> X-Requested-With: ShockwaveFlash/19.0.0.226
> Accept: */*
> DNT: 1
> Referer: http://www.hotstar.com/
> Accept-Encoding: gzip
> Accept-Language: en-US,en;q=0.8,bg;q=0.6
> Cookie: _alid_=PmjLqgcUUqw6TP5gtK/xbg==;
> hdntl=exp=1446809835~acl=%2f*~data=hdntl~hmac=ebaedb13781605ce7f9f26b84e1346a7d43ecf0dfcc99e6b53e32487565ba3f8
> If-Modified-Since: Thu, 05 Nov 2015 02:30:28 GMT
> + Incoming O.S. Response +
> -- State Machine Id: 168
> HTTP/1.1 200 OK
> Server: AkamaiGHost
> Mime-Version: 1.0
> Content-Type: video/abst
> Content-Length: 122
> Last-Modified: Thu, 05 Nov 2015 02:30:28 GMT
> Expires: Thu, 05 Nov 2015 11:38:01 GMT
> Cache-Control: max-age=0, no-cache
> Pragma: no-cache
> Date: Thu, 05 Nov 2015 11:38:01 GMT
> Connection: keep-alive
> Set-Cookie: _alid_=PmjLqgcUUqw6TP5gtK/xbg==;
> path=/z/delayed/indvsa2015_INDVSSATEST1DAY1_1@336263/;
> domain=sshds5-lh.akamaihd.net
> + Base Header for Building Response +
> -- State Machine Id: 168
> HTTP/1.1 200 OK
> Server: AkamaiGHost
> Mime-Version: 1.0
> Content-Type: video/abst
> Content-Length: 122
> Last-Modified: Thu, 05 Nov 2015 02:30:28 GMT
> Expires: Thu, 05 Nov 2015 11:38:01 GMT
> Cache-Control: max-age=0, no-cache
> Pragma: no-cache
> Date: Thu, 05 Nov 2015 11:38:01 GMT
> Connection: keep-alive
> Set-Cookie: _alid_=PmjLqgcUUqw6TP5gtK/xbg==;
> path=/z/delayed/indvsa2015_INDVSSATEST1DAY1_1@336263/;
> domain=sshds5-lh.akamaihd.net
> + Proxy's Response 2 +
> -- State Machine Id: 168
> HTTP/1.1 304 Not Modified
> Date: Thu, 05 Nov 2015 11:38:01 GMT
> Expi
