[jira] [Updated] (TS-3161) traffic_top shows some values incorrectly

[ https://issues.apache.org/jira/browse/TS-3161?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Leif Hedstrom updated TS-3161: -- Fix Version/s: (was: 6.0.0) 6.1.0 > traffic_top shows some values incorrectly >

[jira] [Commented] (TS-3801) Correct responses when CLOSED stream receive frames.

[ https://issues.apache.org/jira/browse/TS-3801?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14648691#comment-14648691 ] Leif Hedstrom commented on TS-3801: --- [~masaori] What's your confidence here, should we land

[jira] [Updated] (TS-3801) Correct responses when CLOSED stream receive frames.

[ https://issues.apache.org/jira/browse/TS-3801?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Leif Hedstrom updated TS-3801: -- Assignee: Masaori Koshiba > Correct responses when CLOSED stream receive frames. >

[jira] [Updated] (TS-3806) In cmd/traffic_manager: libwccp.a(WccpMsg.o): undefined reference to symbol MD5_Final

[ https://issues.apache.org/jira/browse/TS-3806?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Leif Hedstrom updated TS-3806: -- Backport to Version: 5.3.2 > In cmd/traffic_manager: libwccp.a(WccpMsg.o): undefined reference to symbol >

[jira] [Updated] (TS-2150) Add Milestone log tags

[ https://issues.apache.org/jira/browse/TS-2150?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Leif Hedstrom updated TS-2150: -- Fix Version/s: (was: 6.1.0) 6.0.0 > Add Milestone log tags > --

[jira] [Updated] (TS-3786) Use a consensus algorithm to elect the cluster master

[ https://issues.apache.org/jira/browse/TS-3786?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Leif Hedstrom updated TS-3786: -- Fix Version/s: (was: 6.1.0) 6.0.0 > Use a consensus algorithm to elect the cluster m

[jira] [Resolved] (TS-3786) Use a consensus algorithm to elect the cluster master

[ https://issues.apache.org/jira/browse/TS-3786?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Leif Hedstrom resolved TS-3786. --- Resolution: Fixed > Use a consensus algorithm to elect the cluster master > -

[jira] [Updated] (TS-3718) Unused members in LogFile.h

[ https://issues.apache.org/jira/browse/TS-3718?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Leif Hedstrom updated TS-3718: -- Assignee: Daniel Xu > Unused members in LogFile.h > --- > > Key: TS

[jira] [Updated] (TS-3718) Unused members in LogFile.h

[ https://issues.apache.org/jira/browse/TS-3718?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Leif Hedstrom updated TS-3718: -- Fix Version/s: (was: 6.1.0) 6.0.0 > Unused members in LogFile.h > --

[jira] [Updated] (TS-3693) Move 100-continue logic to read client header for intercept plugins

[ https://issues.apache.org/jira/browse/TS-3693?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Leif Hedstrom updated TS-3693: -- Fix Version/s: (was: 6.1.0) 6.0.0 > Move 100-continue logic to read client header fo

[jira] [Updated] (TS-3575) Make an option for traffic_layout to reproduce the configure invocation

[ https://issues.apache.org/jira/browse/TS-3575?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Leif Hedstrom updated TS-3575: -- Fix Version/s: (was: 6.1.0) 6.0.0 > Make an option for traffic_layout to reproduce t

[jira] [Resolved] (TS-3575) Make an option for traffic_layout to reproduce the configure invocation

[ https://issues.apache.org/jira/browse/TS-3575?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Leif Hedstrom resolved TS-3575. --- Resolution: Fixed > Make an option for traffic_layout to reproduce the configure invocation > ---

[jira] [Updated] (TS-3534) Wiretracing for SSL connections

[ https://issues.apache.org/jira/browse/TS-3534?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Leif Hedstrom updated TS-3534: -- Fix Version/s: (was: 6.1.0) 6.0.0 > Wiretracing for SSL connections > --

[jira] [Commented] (TS-3478) Indexing header representations on HPACK encoder

[ https://issues.apache.org/jira/browse/TS-3478?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14648735#comment-14648735 ] Leif Hedstrom commented on TS-3478: --- Cool, moving it out for 6.1.0, I'll land this after we

[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: -- Fix Version/s: (was: 6.0.0) 6.1.0 > Indexing header representations on HPACK encoder

[jira] [Updated] (TS-3804) ASAN heap-use-after-free in HttpClientSession::destroy

[ https://issues.apache.org/jira/browse/TS-3804?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Leif Hedstrom updated TS-3804: -- Fix Version/s: (was: 6.0.0) 6.1.0 > ASAN heap-use-after-free in HttpClientSession::d

[jira] [Updated] (TS-3805) ASAN heap-use-after-free in ProxyClientSession::ssn_hook_get

[ https://issues.apache.org/jira/browse/TS-3805?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Leif Hedstrom updated TS-3805: -- Fix Version/s: (was: 6.0.0) 6.1.0 > ASAN heap-use-after-free in ProxyClientSession::

[jira] [Updated] (TS-1007) SSN Close called before TXN Close

[ https://issues.apache.org/jira/browse/TS-1007?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Leif Hedstrom updated TS-1007: -- Fix Version/s: (was: 6.0.0) 6.1.0 > SSN Close called before TXN Close >

[jira] [Updated] (TS-3805) ASAN heap-use-after-free in ProxyClientSession::ssn_hook_get

[ https://issues.apache.org/jira/browse/TS-3805?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Leif Hedstrom updated TS-3805: -- Assignee: Susan Hinrichs > ASAN heap-use-after-free in ProxyClientSession::ssn_hook_get > -

[jira] [Commented] (TS-3693) Move 100-continue logic to read client header for intercept plugins

[ https://issues.apache.org/jira/browse/TS-3693?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14649253#comment-14649253 ] Leif Hedstrom commented on TS-3693: --- [~bcall] Should we revert this for now? > Move 100-co

[jira] [Commented] (TS-3782) Add tests for HTTP/2 in TSQA

[ https://issues.apache.org/jira/browse/TS-3782?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14649254#comment-14649254 ] Leif Hedstrom commented on TS-3782: --- [~jacksontj] Ping? > Add tests for HTTP/2 in TSQA > -

[jira] [Commented] (TS-2150) Add Milestone log tags

[ https://issues.apache.org/jira/browse/TS-2150?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14649252#comment-14649252 ] Leif Hedstrom commented on TS-2150: --- Is this now completed ? > Add Milestone log tags > --

[jira] [Commented] (TS-3796) Health check fails once (consistently?) during startup

[ https://issues.apache.org/jira/browse/TS-3796?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14649319#comment-14649319 ] Leif Hedstrom commented on TS-3796: --- I see this in the logs: {code} 20150731.07h27m03s RES

[jira] [Updated] (TS-3796) Health check fails once (consistently?) during startup

[ https://issues.apache.org/jira/browse/TS-3796?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Leif Hedstrom updated TS-3796: -- Fix Version/s: (was: 6.1.0) 6.0.0 > Health check fails once (consistently?) during s

[jira] [Comment Edited] (TS-3796) Health check fails once (consistently?) during startup

[ https://issues.apache.org/jira/browse/TS-3796?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14649319#comment-14649319 ] Leif Hedstrom edited comment on TS-3796 at 7/31/15 3:16 PM: I see

[jira] [Created] (TS-3810) traffic_manager leaks the stack from synthetic threads

Leif Hedstrom created TS-3810: - Summary: traffic_manager leaks the stack from synthetic threads Key: TS-3810 URL: https://issues.apache.org/jira/browse/TS-3810 Project: Traffic Server Issue Type:

[jira] [Assigned] (TS-3810) traffic_manager leaks the stack from synthetic threads

[ https://issues.apache.org/jira/browse/TS-3810?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Leif Hedstrom reassigned TS-3810: - Assignee: Leif Hedstrom > traffic_manager leaks the stack from synthetic threads > -

[jira] [Updated] (TS-3810) traffic_manager leaks the stack from synthetic threads

[ https://issues.apache.org/jira/browse/TS-3810?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Leif Hedstrom updated TS-3810: -- Fix Version/s: 6.0.0 > traffic_manager leaks the stack from synthetic threads > ---

[jira] [Resolved] (TS-3810) traffic_manager leaks the stack from synthetic threads

[ https://issues.apache.org/jira/browse/TS-3810?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Leif Hedstrom resolved TS-3810. --- Resolution: Fixed > traffic_manager leaks the stack from synthetic threads >

[jira] [Updated] (TS-3776) traffic_server failed assert `s->current.server->had_connect_fail()`

[ https://issues.apache.org/jira/browse/TS-3776?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Leif Hedstrom updated TS-3776: -- Fix Version/s: (was: 6.1.0) 6.0.0 > traffic_server failed assert `s->current.server-

[jira] [Reopened] (TS-3440) Connect_retries re-connects even if request made it to origin

[ https://issues.apache.org/jira/browse/TS-3440?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Leif Hedstrom reopened TS-3440: --- > Connect_retries re-connects even if request made it to origin > ---

[jira] [Updated] (TS-3801) Correct responses when CLOSED stream receive frames.

[ https://issues.apache.org/jira/browse/TS-3801?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Leif Hedstrom updated TS-3801: -- Fix Version/s: 6.0.0 > Correct responses when CLOSED stream receive frames. > -

[jira] [Updated] (TS-3814) Treat requests with Connection header field as malformed

[ https://issues.apache.org/jira/browse/TS-3814?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Leif Hedstrom updated TS-3814: -- Fix Version/s: 6.0.0 > Treat requests with Connection header field as malformed > -

[jira] [Commented] (TS-3801) Correct responses when CLOSED stream receive frames.

[ https://issues.apache.org/jira/browse/TS-3801?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14652299#comment-14652299 ] Leif Hedstrom commented on TS-3801: --- [~masaori] Should we land this for 6.0.0, or wait unti

[jira] [Commented] (TS-3776) traffic_server failed assert `s->current.server->had_connect_fail()`

[ https://issues.apache.org/jira/browse/TS-3776?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14652302#comment-14652302 ] Leif Hedstrom commented on TS-3776: --- So, this still asserts for me (and I think James too).

[jira] [Reopened] (TS-3440) Connect_retries re-connects even if request made it to origin

[ https://issues.apache.org/jira/browse/TS-3440?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Leif Hedstrom reopened TS-3440: --- > Connect_retries re-connects even if request made it to origin > ---

[jira] [Reopened] (TS-3776) traffic_server failed assert `s->current.server->had_connect_fail()`

[ https://issues.apache.org/jira/browse/TS-3776?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Leif Hedstrom reopened TS-3776: --- > traffic_server failed assert `s->current.server->had_connect_fail()` >

[jira] [Updated] (TS-3796) Health check fails once (consistently?) during startup

[ https://issues.apache.org/jira/browse/TS-3796?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Leif Hedstrom updated TS-3796: -- Assignee: James Peach (was: Leif Hedstrom) > Health check fails once (consistently?) during startup >

[jira] [Updated] (TS-3776) traffic_server failed assert `s->current.server->had_connect_fail()`

[ https://issues.apache.org/jira/browse/TS-3776?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Leif Hedstrom updated TS-3776: -- Fix Version/s: (was: 6.1.0) 6.0.0 > traffic_server failed assert `s->current.server-

[jira] [Commented] (TS-3776) traffic_server failed assert `s->current.server->had_connect_fail()`

[ https://issues.apache.org/jira/browse/TS-3776?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14652458#comment-14652458 ] Leif Hedstrom commented on TS-3776: --- It seems this is also related / triggered by TS-3796,

[jira] [Resolved] (TS-3440) Connect_retries re-connects even if request made it to origin

[ https://issues.apache.org/jira/browse/TS-3440?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Leif Hedstrom resolved TS-3440. --- Resolution: Fixed Closing this for now, since we're tracking the assert in a different Jira. > Connect_r

[jira] [Resolved] (TS-2150) Add Milestone log tags

[ https://issues.apache.org/jira/browse/TS-2150?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Leif Hedstrom resolved TS-2150. --- Resolution: Fixed Closing this as fixed, since there's nothing indicating otherwise. > Add Milestone log

[jira] [Created] (TS-3816) Should we replace ptr_len_cmp() with memcmp() consistently?

Leif Hedstrom created TS-3816: - Summary: Should we replace ptr_len_cmp() with memcmp() consistently? Key: TS-3816 URL: https://issues.apache.org/jira/browse/TS-3816 Project: Traffic Server Issue

[jira] [Updated] (TS-3816) Should we replace ptr_len_cmp() with memcmp() consistently?

[ https://issues.apache.org/jira/browse/TS-3816?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Leif Hedstrom updated TS-3816: -- Labels: newbie++ (was: ) > Should we replace ptr_len_cmp() with memcmp() consistently? > -

[jira] [Updated] (TS-3816) Should we replace ptr_len_cmp() with memcmp() consistently?

[ https://issues.apache.org/jira/browse/TS-3816?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Leif Hedstrom updated TS-3816: -- Fix Version/s: 6.1.0 > Should we replace ptr_len_cmp() with memcmp() consistently? > --

[jira] [Commented] (TS-3814) Treat requests with Connection header field as malformed

[ https://issues.apache.org/jira/browse/TS-3814?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14652739#comment-14652739 ] Leif Hedstrom commented on TS-3814: --- Are you sure you can't just do e.g. {code} diff --git

[jira] [Commented] (TS-3801) Correct responses when CLOSED stream receive frames.

[ https://issues.apache.org/jira/browse/TS-3801?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14652960#comment-14652960 ] Leif Hedstrom commented on TS-3801: --- Alright, I'll review and commit. > Correct responses

[jira] [Resolved] (TS-3801) Correct responses when CLOSED stream receive frames.

[ https://issues.apache.org/jira/browse/TS-3801?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Leif Hedstrom resolved TS-3801. --- Resolution: Fixed > Correct responses when CLOSED stream receive frames. > --

[jira] [Commented] (TS-3497) Malformed requests must be treated as a stream error

[ https://issues.apache.org/jira/browse/TS-3497?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14652965#comment-14652965 ] Leif Hedstrom commented on TS-3497: --- Is this a 6.0.0 candidate as well? Or leave it out for

[jira] [Updated] (TS-3497) Malformed requests must be treated as a stream error

[ https://issues.apache.org/jira/browse/TS-3497?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Leif Hedstrom updated TS-3497: -- Fix Version/s: (was: 6.1.0) 6.0.0 > Malformed requests must be treated as a stream e

[jira] [Commented] (TS-3752) Problem with larger headers and HTTP/2

[ https://issues.apache.org/jira/browse/TS-3752?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14652966#comment-14652966 ] Leif Hedstrom commented on TS-3752: --- [~masaori] Should we expect a fix for this for 6.0.0,

[jira] [Commented] (TS-3752) Problem with larger headers and HTTP/2

[ https://issues.apache.org/jira/browse/TS-3752?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14652988#comment-14652988 ] Leif Hedstrom commented on TS-3752: --- Alright. My hope / goal is that we can spin off a 6.0.

[jira] [Updated] (TS-3752) Problem with larger headers and HTTP/2

[ https://issues.apache.org/jira/browse/TS-3752?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Leif Hedstrom updated TS-3752: -- Fix Version/s: (was: 6.1.0) 6.0.0 > Problem with larger headers and HTTP/2 > ---

[jira] [Updated] (TS-3817) Assertion on non (HTTP/S WS/S) request scheme in debug mode

[ https://issues.apache.org/jira/browse/TS-3817?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Leif Hedstrom updated TS-3817: -- Fix Version/s: 6.0.0 > Assertion on non (HTTP/S WS/S) request scheme in debug mode > --

[jira] [Commented] (TS-3817) Assertion on non (HTTP/S WS/S) request scheme in debug mode

[ https://issues.apache.org/jira/browse/TS-3817?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14653876#comment-14653876 ] Leif Hedstrom commented on TS-3817: --- Done. [~ushachar] Thanks for the fix. But please remem

[jira] [Commented] (TS-3799) Padded DATA frames lead to PROTOCOL_ERROR

[ https://issues.apache.org/jira/browse/TS-3799?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14653982#comment-14653982 ] Leif Hedstrom commented on TS-3799: --- [~masaori] Can you take a look at this, and give a rec

[jira] [Updated] (TS-3799) Padded DATA frames lead to PROTOCOL_ERROR

[ https://issues.apache.org/jira/browse/TS-3799?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Leif Hedstrom updated TS-3799: -- Assignee: Masaori Koshiba (was: Leif Hedstrom) > Padded DATA frames lead to PROTOCOL_ERROR > -

[jira] [Commented] (TS-3811) HTTP/2 window size must not exceed 2^31-1

[ https://issues.apache.org/jira/browse/TS-3811?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14653987#comment-14653987 ] Leif Hedstrom commented on TS-3811: --- [~masaori] Since we'll land TS-3497 for 6.0.0, should

[jira] [Updated] (TS-3811) HTTP/2 window size must not exceed 2^31-1

[ https://issues.apache.org/jira/browse/TS-3811?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Leif Hedstrom updated TS-3811: -- Assignee: Masaori Koshiba > HTTP/2 window size must not exceed 2^31-1 > ---

[jira] [Updated] (TS-3811) HTTP/2 window size must not exceed 2^31-1

[ https://issues.apache.org/jira/browse/TS-3811?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Leif Hedstrom updated TS-3811: -- Fix Version/s: 6.0.0 > HTTP/2 window size must not exceed 2^31-1 >

[jira] [Commented] (TS-3814) Treat requests with Connection header field as malformed

[ https://issues.apache.org/jira/browse/TS-3814?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14653989#comment-14653989 ] Leif Hedstrom commented on TS-3814: --- [~masaori] [~rokubo] Any thoughts on my comment? > Tr

[jira] [Updated] (TS-3812) Trailing Header Support in HTTP/2

[ https://issues.apache.org/jira/browse/TS-3812?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Leif Hedstrom updated TS-3812: -- Fix Version/s: 6.1.0 > Trailing Header Support in HTTP/2 > - > >

[jira] [Updated] (TS-3813) Correct responses when half-closed stream receive frames

[ https://issues.apache.org/jira/browse/TS-3813?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Leif Hedstrom updated TS-3813: -- Fix Version/s: 6.1.0 > Correct responses when half-closed stream receive frames > -

[jira] [Comment Edited] (TS-3814) Treat requests with Connection header field as malformed

[ https://issues.apache.org/jira/browse/TS-3814?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14653989#comment-14653989 ] Leif Hedstrom edited comment on TS-3814 at 8/4/15 5:23 PM: --- [~masao

[jira] [Commented] (TS-3497) Malformed requests must be treated as a stream error

[ https://issues.apache.org/jira/browse/TS-3497?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14654078#comment-14654078 ] Leif Hedstrom commented on TS-3497: --- I spoke with [~jpe...@apache.org] on this, and we agre

[jira] [Comment Edited] (TS-3497) Malformed requests must be treated as a stream error

[ https://issues.apache.org/jira/browse/TS-3497?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14654078#comment-14654078 ] Leif Hedstrom edited comment on TS-3497 at 8/4/15 6:14 PM: --- I spoke

[jira] [Commented] (TS-3782) Add tests for HTTP/2 in TSQA

[ https://issues.apache.org/jira/browse/TS-3782?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14654694#comment-14654694 ] Leif Hedstrom commented on TS-3782: --- Can we close this, or is there more to come in the 6.0

[jira] [Commented] (TS-3814) Treat requests with Connection header field as malformed

[ https://issues.apache.org/jira/browse/TS-3814?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14654699#comment-14654699 ] Leif Hedstrom commented on TS-3814: --- Great, thanks. I'm going to commit this one, and close

[jira] [Comment Edited] (TS-3814) Treat requests with Connection header field as malformed

[ https://issues.apache.org/jira/browse/TS-3814?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14654699#comment-14654699 ] Leif Hedstrom edited comment on TS-3814 at 8/5/15 2:19 AM: --- Great,

[jira] [Updated] (TS-3799) Padded DATA frames lead to PROTOCOL_ERROR

[ https://issues.apache.org/jira/browse/TS-3799?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Leif Hedstrom updated TS-3799: -- Fix Version/s: (was: 6.1.0) 6.0.0 > Padded DATA frames lead to PROTOCOL_ERROR >

[jira] [Created] (TS-3820) Change default for proxy.config.http.redirect_host_no_port (to 1, enabled)

Leif Hedstrom created TS-3820: - Summary: Change default for proxy.config.http.redirect_host_no_port (to 1, enabled) Key: TS-3820 URL: https://issues.apache.org/jira/browse/TS-3820 Project: Traffic Server

[jira] [Updated] (TS-3820) Change default for proxy.config.http.redirect_host_no_port (to 1, enabled)

[ https://issues.apache.org/jira/browse/TS-3820?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Leif Hedstrom updated TS-3820: -- Fix Version/s: 6.0.0 > Change default for proxy.config.http.redirect_host_no_port (to 1, enabled) > ---

[jira] [Assigned] (TS-3820) Change default for proxy.config.http.redirect_host_no_port (to 1, enabled)

[ https://issues.apache.org/jira/browse/TS-3820?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Leif Hedstrom reassigned TS-3820: - Assignee: Leif Hedstrom > Change default for proxy.config.http.redirect_host_no_port (to 1, enabled)

[jira] [Updated] (TS-3658) ASAN triggers when using the escalate.so plugin

[ https://issues.apache.org/jira/browse/TS-3658?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Leif Hedstrom updated TS-3658: -- Fix Version/s: (was: 6.1.0) 6.0.0 > ASAN triggers when using the escalate.so plugin

[jira] [Commented] (TS-3497) Malformed requests must be treated as a stream error

[ https://issues.apache.org/jira/browse/TS-3497?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14658385#comment-14658385 ] Leif Hedstrom commented on TS-3497: --- [~maskit] Unfortunately, this now doesn't apply cleanl

[jira] [Updated] (TS-3820) Change default for proxy.config.http.redirect_host_no_port (to 1, enabled)

[ https://issues.apache.org/jira/browse/TS-3820?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Leif Hedstrom updated TS-3820: -- Assignee: Gancho Tenev (was: Leif Hedstrom) > Change default for proxy.config.http.redirect_host_no_port (

[jira] [Updated] (TS-3821) Segmentation fault possibly due leaks in atscppapi

[ https://issues.apache.org/jira/browse/TS-3821?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Leif Hedstrom updated TS-3821: -- Fix Version/s: 6.1.0 > Segmentation fault possibly due leaks in atscppapi > ---

[jira] [Updated] (TS-3809) Corrupt debug log messages LogFormat::parse_format_string

[ https://issues.apache.org/jira/browse/TS-3809?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Leif Hedstrom updated TS-3809: -- Fix Version/s: 6.1.0 > Corrupt debug log messages LogFormat::parse_format_string >

[jira] [Updated] (TS-3808) ☂ Testing HTTP/2 features by h2spec

[ https://issues.apache.org/jira/browse/TS-3808?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Leif Hedstrom updated TS-3808: -- Fix Version/s: 6.1.0 > ☂ Testing HTTP/2 features by h2spec > > >

[jira] [Updated] (TS-3792) Pointing proxy.config.dns.resolv_conf at an empty (or nonexistant) file causes segmentation faults on first DNS query

[ https://issues.apache.org/jira/browse/TS-3792?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Leif Hedstrom updated TS-3792: -- Fix Version/s: 6.1.0 > Pointing proxy.config.dns.resolv_conf at an empty (or nonexistant) file > causes se

[jira] [Updated] (TS-3819) H2 error logging

[ https://issues.apache.org/jira/browse/TS-3819?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Leif Hedstrom updated TS-3819: -- Fix Version/s: 6.0.0 > H2 error logging > > > Key: TS-3819 >

[jira] [Commented] (TS-3819) H2 error logging

[ https://issues.apache.org/jira/browse/TS-3819?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14658397#comment-14658397 ] Leif Hedstrom commented on TS-3819: --- [~rokubo] Should we land this for 6.0.0, or wait until

[jira] [Commented] (TS-3820) Change default for proxy.config.http.redirect_host_no_port (to 1, enabled)

[ https://issues.apache.org/jira/browse/TS-3820?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14658389#comment-14658389 ] Leif Hedstrom commented on TS-3820: --- [~gancho] Can you test / verify that the code for this

[jira] [Commented] (TS-3782) Add tests for HTTP/2 in TSQA

[ https://issues.apache.org/jira/browse/TS-3782?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14658441#comment-14658441 ] Leif Hedstrom commented on TS-3782: --- Oops, I already merged this. Can you provide a new pul

[jira] [Resolved] (TS-3811) HTTP/2 window size must not exceed 2^31-1

[ https://issues.apache.org/jira/browse/TS-3811?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Leif Hedstrom resolved TS-3811. --- Resolution: Fixed > HTTP/2 window size must not exceed 2^31-1 > -

[jira] [Assigned] (TS-3822) clang-analyzer: Value stored to 'stream' during its initialization is never read

[ https://issues.apache.org/jira/browse/TS-3822?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Leif Hedstrom reassigned TS-3822: - Assignee: Leif Hedstrom > clang-analyzer: Value stored to 'stream' during its initialization is neve

[jira] [Created] (TS-3822) clang-analyzer: Value stored to 'stream' during its initialization is never read

Leif Hedstrom created TS-3822: - Summary: clang-analyzer: Value stored to 'stream' during its initialization is never read Key: TS-3822 URL: https://issues.apache.org/jira/browse/TS-3822 Project: Traffic S

[jira] [Updated] (TS-3822) clang-analyzer: Value stored to 'stream' during its initialization is never read

[ https://issues.apache.org/jira/browse/TS-3822?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Leif Hedstrom updated TS-3822: -- Fix Version/s: 6.0.0 > clang-analyzer: Value stored to 'stream' during its initialization is never > read

[jira] [Commented] (TS-3658) ASAN triggers when using the escalate.so plugin

[ https://issues.apache.org/jira/browse/TS-3658?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14658603#comment-14658603 ] Leif Hedstrom commented on TS-3658: --- I'm gonna make the bare minimal changes for this, to m

[jira] [Assigned] (TS-3823) ASAN makes us forget to add -ldl on the LIBS

[ https://issues.apache.org/jira/browse/TS-3823?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Leif Hedstrom reassigned TS-3823: - Assignee: Leif Hedstrom > ASAN makes us forget to add -ldl on the LIBS > ---

[jira] [Created] (TS-3823) ASAN makes us forget to add -ldl on the LIBS

Leif Hedstrom created TS-3823: - Summary: ASAN makes us forget to add -ldl on the LIBS Key: TS-3823 URL: https://issues.apache.org/jira/browse/TS-3823 Project: Traffic Server Issue Type: Bug

[jira] [Updated] (TS-3823) ASAN makes us forget to add -ldl on the LIBS

[ https://issues.apache.org/jira/browse/TS-3823?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Leif Hedstrom updated TS-3823: -- Backport to Version: 5.3.2 > ASAN makes us forget to add -ldl on the LIBS > ---

[jira] [Updated] (TS-3823) ASAN makes us forget to add -ldl on the LIBS

[ https://issues.apache.org/jira/browse/TS-3823?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Leif Hedstrom updated TS-3823: -- Fix Version/s: 6.0.0 > ASAN makes us forget to add -ldl on the LIBS > -

[jira] [Commented] (TS-3823) ASAN makes us forget to add -ldl on the LIBS

[ https://issues.apache.org/jira/browse/TS-3823?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14658762#comment-14658762 ] Leif Hedstrom commented on TS-3823: --- I'm also marking this as a suggested backoprt for v5.3

[jira] [Resolved] (TS-3823) ASAN makes us forget to add -ldl on the LIBS

[ https://issues.apache.org/jira/browse/TS-3823?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Leif Hedstrom resolved TS-3823. --- Resolution: Fixed > ASAN makes us forget to add -ldl on the LIBS > --

[jira] [Commented] (TS-3823) ASAN makes us forget to add -ldl on the LIBS

[ https://issues.apache.org/jira/browse/TS-3823?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14658862#comment-14658862 ] Leif Hedstrom commented on TS-3823: --- I think both of these should be considered for 5.3.2,

[jira] [Reopened] (TS-3823) ASAN makes us forget to add -ldl on the LIBS

[ https://issues.apache.org/jira/browse/TS-3823?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Leif Hedstrom reopened TS-3823: --- Breaks on FBSD10 > ASAN makes us forget to add -ldl on the LIBS > -

[jira] [Created] (TS-3824) Wrong #include of pcre.h in a couple of plugins

Leif Hedstrom created TS-3824: - Summary: Wrong #include of pcre.h in a couple of plugins Key: TS-3824 URL: https://issues.apache.org/jira/browse/TS-3824 Project: Traffic Server Issue Type: Bug

[jira] [Assigned] (TS-3824) Wrong #include of pcre.h in a couple of plugins

[ https://issues.apache.org/jira/browse/TS-3824?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Leif Hedstrom reassigned TS-3824: - Assignee: Leif Hedstrom > Wrong #include of pcre.h in a couple of plugins >

[jira] [Updated] (TS-3824) Wrong #include of pcre.h in a couple of plugins

[ https://issues.apache.org/jira/browse/TS-3824?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Leif Hedstrom updated TS-3824: -- Fix Version/s: 6.0.0 > Wrong #include of pcre.h in a couple of plugins > --

<    5   6   7   8   9   10   11   12   13   14   >