[jira] [Commented] (TS-3596) TSHttpTxnPluginTagGet() returns fetchSM over H2

[ https://issues.apache.org/jira/browse/TS-3596?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14540150#comment-14540150 ] Scott Beardsley commented on TS-3596: - Is there a better api which returns whether H1,

[jira] [Commented] (TS-2609) Header rewrite plugin *URL:HOST condition

[ https://issues.apache.org/jira/browse/TS-2609?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14540272#comment-14540272 ] ASF subversion and git services commented on TS-2609: - Commit

[jira] [Updated] (TS-2032) Set milestone for cache-lookup times

[ https://issues.apache.org/jira/browse/TS-2032?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] John updated TS-2032: - Attachment: TS-2032.diff Obsolete code and comments removed. Set milestone for cache-lookup times

[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-tabpanelfocusedCommentId=14540349#comment-14540349 ] ASF subversion and git services commented on TS-3584: - Commit

[jira] [Commented] (TS-2032) Set milestone for cache-lookup times

[ https://issues.apache.org/jira/browse/TS-2032?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14540372#comment-14540372 ] John commented on TS-2032: -- It was decided that this milestone is not needed and that the todo for

[jira] [Resolved] (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:all-tabpanel ] Susan Hinrichs resolved TS-3584. Resolution: Fixed I explicitly added the Connection: close header for both SPDY and H2. We have been

[jira] [Commented] (TS-2325) remap.config .include should support directories

[ https://issues.apache.org/jira/browse/TS-2325?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14540541#comment-14540541 ] Leif Hedstrom commented on TS-2325: --- Over to [~jpe...@apache.org] again, sorry for the

[jira] [Updated] (TS-2325) remap.config .include should support directories

[ https://issues.apache.org/jira/browse/TS-2325?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Leif Hedstrom updated TS-2325: -- Assignee: James Peach (was: Leif Hedstrom) remap.config .include should support directories

[jira] [Commented] (TS-3578) Rearrange Client Session processing to give access to socket at SSN_CLOSE for all protocols

[ https://issues.apache.org/jira/browse/TS-3578?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14540472#comment-14540472 ] Susan Hinrichs commented on TS-3578: This rearrangement has worked well. For SSN_CLOSE,

[jira] [Commented] (TS-2151) Do we really need HttpSM::_instantiate_func() now?

[ https://issues.apache.org/jira/browse/TS-2151?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14540506#comment-14540506 ] Leif Hedstrom commented on TS-2151: --- I did some quick benchmark, exercising a lot of HttpSM

[jira] [Updated] (TS-2258) Verify that all fields are correct in RecordsConfig.cc

[ https://issues.apache.org/jira/browse/TS-2258?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Leif Hedstrom updated TS-2258: -- Assignee: (was: Leif Hedstrom) Verify that all fields are correct in RecordsConfig.cc

[jira] [Updated] (TS-2258) Verify that all fields are correct in RecordsConfig.cc

[ https://issues.apache.org/jira/browse/TS-2258?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Leif Hedstrom updated TS-2258: -- Labels: newbie (was: ) Verify that all fields are correct in RecordsConfig.cc

[jira] [Commented] (TS-3589) Enhance header_rewrite to support TRANSACT_COUNT as a condition

[ https://issues.apache.org/jira/browse/TS-3589?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14540253#comment-14540253 ] ASF GitHub Bot commented on TS-3589: GitHub user ericcarlschwartz opened a pull request:

[jira] [Updated] (TS-2032) Set milestone for cache-lookup times

[ https://issues.apache.org/jira/browse/TS-2032?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] John updated TS-2032: - Attachment: (was: TS-2032.diff) Set milestone for cache-lookup times

[jira] [Updated] (TS-61) Multiple do_io_pread on a CacheVConnection

[ https://issues.apache.org/jira/browse/TS-61?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Phil Sorber updated TS-61: -- Fix Version/s: (was: 5.3.0) Multiple do_io_pread on a CacheVConnection

[jira] [Reopened] (TS-61) Multiple do_io_pread on a CacheVConnection

[ https://issues.apache.org/jira/browse/TS-61?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Phil Sorber reopened TS-61: --- Multiple do_io_pread on a CacheVConnection -- Key: TS-61

[jira] [Resolved] (TS-61) Multiple do_io_pread on a CacheVConnection

[ https://issues.apache.org/jira/browse/TS-61?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Phil Sorber resolved TS-61. --- Resolution: Won't Fix Multiple do_io_pread on a CacheVConnection --

[jira] [Updated] (TS-2644) TOS (DSCP)

[ https://issues.apache.org/jira/browse/TS-2644?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Phil Sorber updated TS-2644: Fix Version/s: (was: 5.3.0) TOS (DSCP) --- Key: TS-2644 URL:

[jira] [Updated] (TS-3597) TLS can fail accept / handshake since commit 2a8bb593fd

[ https://issues.apache.org/jira/browse/TS-3597?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Leif Hedstrom updated TS-3597: -- Fix Version/s: 6.0.0 TLS can fail accept / handshake since commit 2a8bb593fd

[jira] [Updated] (TS-3597) TLS can fail accept / handshake since commit 2a8bb593fd

[ https://issues.apache.org/jira/browse/TS-3597?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Leif Hedstrom updated TS-3597: -- Priority: Critical (was: Major) TLS can fail accept / handshake since commit 2a8bb593fd

[jira] [Updated] (TS-3335) Can we eliminate proxy.config.url_remap.url_remap_mode ?

[ https://issues.apache.org/jira/browse/TS-3335?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Leif Hedstrom updated TS-3335: -- Assignee: Phil Sorber (was: Leif Hedstrom) Can we eliminate proxy.config.url_remap.url_remap_mode ?

[jira] [Updated] (TS-481) Poorly handled remap with proxy.config.url_remap.url_remap_mode set to 2

[ https://issues.apache.org/jira/browse/TS-481?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Leif Hedstrom updated TS-481: - Summary: Poorly handled remap with proxy.config.url_remap.url_remap_mode set to 2 (was: Missing remap

[jira] [Commented] (TS-2032) Set milestone for cache-lookup times

[ https://issues.apache.org/jira/browse/TS-2032?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14539917#comment-14539917 ] John commented on TS-2032: -- Attached is my patch for TS-2032. I added an http stat milestone called

[jira] [Updated] (TS-2032) Set milestone for cache-lookup times

[ https://issues.apache.org/jira/browse/TS-2032?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] John updated TS-2032: - Attachment: TS-2032.diff Diff for changes noted above. Set milestone for cache-lookup times

[jira] [Updated] (TS-464) Chunked response with bad Content-Length header to HTTP/1.0 client is broken

[ https://issues.apache.org/jira/browse/TS-464?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Leif Hedstrom updated TS-464: - Assignee: (was: Leif Hedstrom) Chunked response with bad Content-Length header to HTTP/1.0 client is

[jira] [Commented] (TS-3335) Can we eliminate proxy.config.url_remap.url_remap_mode ?

[ https://issues.apache.org/jira/browse/TS-3335?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14539885#comment-14539885 ] Leif Hedstrom commented on TS-3335: --- It seems that this is indeed a real use case. When set

[jira] [Updated] (TS-3335) Can we eliminate proxy.config.url_remap.url_remap_mode ?

[ https://issues.apache.org/jira/browse/TS-3335?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Leif Hedstrom updated TS-3335: -- Fix Version/s: (was: 6.0.0) Can we eliminate proxy.config.url_remap.url_remap_mode ?

[jira] [Commented] (TS-481) Missing remap support for two cases

[ https://issues.apache.org/jira/browse/TS-481?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14539889#comment-14539889 ] Leif Hedstrom commented on TS-481: -- I think #2 is fixed, and #1 is duplicated by TS-3335.

[jira] [Resolved] (TS-3335) Can we eliminate proxy.config.url_remap.url_remap_mode ?

[ https://issues.apache.org/jira/browse/TS-3335?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Leif Hedstrom resolved TS-3335. --- Resolution: Duplicate Can we eliminate proxy.config.url_remap.url_remap_mode ?

[jira] [Updated] (TS-481) Poorly handled remap with proxy.config.url_remap.url_remap_mode set to 2

[ https://issues.apache.org/jira/browse/TS-481?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Leif Hedstrom updated TS-481: - Assignee: Phil Sorber (was: Leif Hedstrom) Poorly handled remap with proxy.config.url_remap.url_remap_mode

[jira] [Comment Edited] (TS-2032) Set milestone for cache-lookup times

[ https://issues.apache.org/jira/browse/TS-2032?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14539917#comment-14539917 ] John edited comment on TS-2032 at 5/12/15 2:41 PM: --- Attached is my patch

[jira] [Commented] (TS-3597) TLS can fail accept / handshake since commit 2a8bb593fd

[ https://issues.apache.org/jira/browse/TS-3597?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14541347#comment-14541347 ] Leif Hedstrom commented on TS-3597: --- Also from [~gancho], when this reproduces, a command

[jira] [Updated] (TS-3597) TLS can fail accept / handshake since commit 2a8bb593fd

[ https://issues.apache.org/jira/browse/TS-3597?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Leif Hedstrom updated TS-3597: -- Backport to Version: 5.3.1 TLS can fail accept / handshake since commit 2a8bb593fd

[jira] [Commented] (TS-3597) TLS can fail accept / handshake since commit 2a8bb593fd

[ https://issues.apache.org/jira/browse/TS-3597?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14541340#comment-14541340 ] Leif Hedstrom commented on TS-3597: --- I'm going to mark this for v5.3.1 back port as well

[jira] [Updated] (TS-3597) TLS can fail accept / handshake since commit 2a8bb593fd

[ https://issues.apache.org/jira/browse/TS-3597?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Leif Hedstrom updated TS-3597: -- Description: At least under certain conditions (slightly unclear,but possible a race with multiple NUMA

[jira] [Issue Comment Deleted] (TS-3597) TLS can fail accept / handshake since commit 2a8bb593fd

[ https://issues.apache.org/jira/browse/TS-3597?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Leif Hedstrom updated TS-3597: -- Comment: was deleted (was: Also from [~gancho], when this reproduces, a command like e.g. this will fail

[jira] [Created] (TS-3597) TLS can fail accept / handshake since commit 2a8bb593fd

Leif Hedstrom created TS-3597: - Summary: TLS can fail accept / handshake since commit 2a8bb593fd Key: TS-3597 URL: https://issues.apache.org/jira/browse/TS-3597 Project: Traffic Server Issue

[jira] [Updated] (TS-3597) TLS can fail accept / handshake since commit 2a8bb593fd

[ https://issues.apache.org/jira/browse/TS-3597?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Leif Hedstrom updated TS-3597: -- Description: At least under certain conditions (slightly unclear,but possible a race with multiple NUMA

[jira] [Updated] (TS-481) Poorly handled remap with proxy.config.url_remap.url_remap_mode set to 2

[ https://issues.apache.org/jira/browse/TS-481?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Phil Sorber updated TS-481: --- Assignee: John (was: Phil Sorber) Poorly handled remap with proxy.config.url_remap.url_remap_mode set to 2

[jira] [Commented] (TS-3578) Rearrange Client Session processing to give access to socket at SSN_CLOSE for all protocols

[ https://issues.apache.org/jira/browse/TS-3578?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14540059#comment-14540059 ] ASF GitHub Bot commented on TS-3578: Github user shinrich commented on the pull request: