[jira] [Commented] (TS-3960) traffic_line -x doesn't reload SSL certs content
[ https://issues.apache.org/jira/browse/TS-3960?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15003685#comment-15003685 ] ASF GitHub Bot commented on TS-3960: Github user zizhong closed the pull request at: https://github.com/apache/trafficserver/pull/301 > traffic_line -x doesn't reload SSL certs content > > > Key: TS-3960 > URL: https://issues.apache.org/jira/browse/TS-3960 > Project: Traffic Server > Issue Type: Bug > Components: SSL >Reporter: Zhang Zizhong >Assignee: Brian Geffon > Fix For: 6.1.0 > > > traffic_line -x doesn't reload when SSL certs change file contents without > changing the file names. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (TS-3960) traffic_line -x doesn't reload SSL certs content
[ https://issues.apache.org/jira/browse/TS-3960?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15003702#comment-15003702 ] ASF GitHub Bot commented on TS-3960: GitHub user zizhong reopened a pull request: https://github.com/apache/trafficserver/pull/301 TS-3960: traffic_line -x doesn't reload SSL certs content traffic_line -x doesn't reload when SSL certs change file contents without changing the file names. You can merge this pull request into a Git repository by running: $ git pull https://github.com/zizhong/trafficserver sslmuticertreload Alternatively you can review and apply these changes as the patch at: https://github.com/apache/trafficserver/pull/301.patch To close this pull request, make a commit to your master/trunk branch with (at least) the following in the commit message: This closes #301 commit 249dc53472816a6d168266382f699e6eeaeff1af Author: Zizhong Zhang Date: 2015-11-13T08:25:04Z TS-3960: traffic_line -x doesn't reload SSL certs content > traffic_line -x doesn't reload SSL certs content > > > Key: TS-3960 > URL: https://issues.apache.org/jira/browse/TS-3960 > Project: Traffic Server > Issue Type: Bug > Components: SSL >Reporter: Zhang Zizhong >Assignee: Brian Geffon > Fix For: 6.1.0 > > > traffic_line -x doesn't reload when SSL certs change file contents without > changing the file names. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (TS-3960) traffic_line -x doesn't reload SSL certs content
[ https://issues.apache.org/jira/browse/TS-3960?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15003707#comment-15003707 ] ASF GitHub Bot commented on TS-3960: Github user zizhong commented on the pull request: https://github.com/apache/trafficserver/pull/301#issuecomment-156361172 hey @jpeach , I updated the branch with your opinion. Would you mind taking another look at it? > traffic_line -x doesn't reload SSL certs content > > > Key: TS-3960 > URL: https://issues.apache.org/jira/browse/TS-3960 > Project: Traffic Server > Issue Type: Bug > Components: SSL >Reporter: Zhang Zizhong >Assignee: Brian Geffon > Fix For: 6.1.0 > > > traffic_line -x doesn't reload when SSL certs change file contents without > changing the file names. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (TS-4021) Lua Plugin - Expose API Calls TSHttpTxnFollowRedirect()
[ https://issues.apache.org/jira/browse/TS-4021?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jeremy Payne updated TS-4021: - Description: Instead of relying on a config override, this plugin 'new feature' would allow for enabling origin server redirection on the fly; via a direct API call. was:Instead of relying on a config override, this plugin 'new feature' would allow for enabling origin server redirection on the fly; via a direct API call. Summary: Lua Plugin - Expose API Calls TSHttpTxnFollowRedirect() (was: Lua Plugin - Expose API Calls TSHttpTxnFollowRedirect(), TSHttpTxnRedirectUrlSet()) > Lua Plugin - Expose API Calls TSHttpTxnFollowRedirect() > --- > > Key: TS-4021 > URL: https://issues.apache.org/jira/browse/TS-4021 > Project: Traffic Server > Issue Type: New Feature >Reporter: Jeremy Payne > > Instead of relying on a config override, this plugin 'new feature' would > allow for enabling origin server redirection on the fly; via a direct API > call. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (TS-4021) Lua Plugin - Expose API Calls TSHttpTxnFollowRedirect()
[ https://issues.apache.org/jira/browse/TS-4021?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jeremy Payne updated TS-4021: - Affects Version/s: 6.1.0 Priority: Minor (was: Major) > Lua Plugin - Expose API Calls TSHttpTxnFollowRedirect() > --- > > Key: TS-4021 > URL: https://issues.apache.org/jira/browse/TS-4021 > Project: Traffic Server > Issue Type: New Feature >Affects Versions: 6.1.0 >Reporter: Jeremy Payne >Priority: Minor > > Instead of relying on a config override, this plugin 'new feature' would > allow for enabling origin server redirection on the fly; via a direct API > call. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (TS-4021) Lua Plugin - Expose API Call TSHttpTxnFollowRedirect()
[ https://issues.apache.org/jira/browse/TS-4021?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jeremy Payne updated TS-4021: - Summary: Lua Plugin - Expose API Call TSHttpTxnFollowRedirect() (was: Lua Plugin - Expose API Calls TSHttpTxnFollowRedirect()) > Lua Plugin - Expose API Call TSHttpTxnFollowRedirect() > -- > > Key: TS-4021 > URL: https://issues.apache.org/jira/browse/TS-4021 > Project: Traffic Server > Issue Type: New Feature >Affects Versions: 6.1.0 >Reporter: Jeremy Payne >Priority: Minor > > Instead of relying on a config override, this plugin 'new feature' would > allow for enabling origin server redirection on the fly; via a direct API > call. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Created] (TS-4021) Lua Plugin - Expose API Calls TSHttpTxnFollowRedirect(), TSHttpTxnRedirectUrlSet()
Jeremy Payne created TS-4021: Summary: Lua Plugin - Expose API Calls TSHttpTxnFollowRedirect(), TSHttpTxnRedirectUrlSet() Key: TS-4021 URL: https://issues.apache.org/jira/browse/TS-4021 Project: Traffic Server Issue Type: New Feature Reporter: Jeremy Payne Instead of relying on a config override, this plugin 'new feature' would allow for enabling origin server redirection on the fly; via a direct API call. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Created] (TS-4022) Incorrect behavior with remap prefix matching
Daniel Xu created TS-4022: - Summary: Incorrect behavior with remap prefix matching Key: TS-4022 URL: https://issues.apache.org/jira/browse/TS-4022 Project: Traffic Server Issue Type: Bug Components: Remap API Reporter: Daniel Xu If you have two remap rules like this: `map https://localhost:8081/1 https://httpbin.org/html` `map https://localhost:8081/10 https://httpbin.org/html` When connection to `https://localhost:8081/10`, ATS will first replace `https://localhost:8081/1` with `https://httpbin.org/html`, and then append the `0` to the end. So your final URI will look like: `https://httpbin.org/html0` If two remaps are explicitly specified, both should work. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (TS-4022) Incorrect behavior with remap prefix matching
[ https://issues.apache.org/jira/browse/TS-4022?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Daniel Xu updated TS-4022: -- Description: If you have two remap rules like this: `map https://localhost:8081/1 https://httpbin.org/html` `map https://localhost:8081/10 https://httpbin.org/html` When connecting to `https://localhost:8081/10`, ATS will first replace `https://localhost:8081/1` with `https://httpbin.org/html`, and then append the `0` to the end. So your final URI will look like: `https://httpbin.org/html0` If two remaps are explicitly specified, both should work. was: If you have two remap rules like this: `map https://localhost:8081/1 https://httpbin.org/html` `map https://localhost:8081/10 https://httpbin.org/html` When connection to `https://localhost:8081/10`, ATS will first replace `https://localhost:8081/1` with `https://httpbin.org/html`, and then append the `0` to the end. So your final URI will look like: `https://httpbin.org/html0` If two remaps are explicitly specified, both should work. > Incorrect behavior with remap prefix matching > - > > Key: TS-4022 > URL: https://issues.apache.org/jira/browse/TS-4022 > Project: Traffic Server > Issue Type: Bug > Components: Remap API >Reporter: Daniel Xu > > If you have two remap rules like this: > `map https://localhost:8081/1 https://httpbin.org/html` > `map https://localhost:8081/10 https://httpbin.org/html` > When connecting to `https://localhost:8081/10`, ATS will first replace > `https://localhost:8081/1` with `https://httpbin.org/html`, and then append > the `0` to the end. > So your final URI will look like: > `https://httpbin.org/html0` > If two remaps are explicitly specified, both should work. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (TS-4022) Incorrect behavior with remap prefix matching
[ https://issues.apache.org/jira/browse/TS-4022?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Daniel Xu updated TS-4022: -- Description: If you have two remap rules like this: `map https://localhost:8081/1 https://httpbin.org/html` `map https://localhost:8081/10 https://httpbin.org/html` When connecting to `https://localhost:8081/10`, ATS will first replace `https://localhost:8081/1` with `https://httpbin.org/html`, and then append the `0` to the end. So your final URI will look like: `https://httpbin.org/html0`, which should not be the case. If two remaps are explicitly specified, both should work. was: If you have two remap rules like this: `map https://localhost:8081/1 https://httpbin.org/html` `map https://localhost:8081/10 https://httpbin.org/html` When connecting to `https://localhost:8081/10`, ATS will first replace `https://localhost:8081/1` with `https://httpbin.org/html`, and then append the `0` to the end. So your final URI will look like: `https://httpbin.org/html0` , which should not be the case. If two remaps are explicitly specified, both should work. > Incorrect behavior with remap prefix matching > - > > Key: TS-4022 > URL: https://issues.apache.org/jira/browse/TS-4022 > Project: Traffic Server > Issue Type: Bug > Components: Remap API >Reporter: Daniel Xu > > If you have two remap rules like this: > `map https://localhost:8081/1 https://httpbin.org/html` > `map https://localhost:8081/10 https://httpbin.org/html` > When connecting to `https://localhost:8081/10`, ATS will first replace > `https://localhost:8081/1` with `https://httpbin.org/html`, and then append > the `0` to the end. > So your final URI will look like: > `https://httpbin.org/html0`, which should not be the case. > If two remaps are explicitly specified, both should work. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (TS-4022) Incorrect behavior with remap prefix matching
[ https://issues.apache.org/jira/browse/TS-4022?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Daniel Xu updated TS-4022: -- Description: If you have two remap rules like this: `map https://localhost:8081/1 https://httpbin.org/html` `map https://localhost:8081/10 https://httpbin.org/html` When connecting to `https://localhost:8081/10`, ATS will first replace `https://localhost:8081/1` with `https://httpbin.org/html`, and then append the `0` to the end. So your final URI will look like: `https://httpbin.org/html0` , which should not be the case. If two remaps are explicitly specified, both should work. was: If you have two remap rules like this: `map https://localhost:8081/1 https://httpbin.org/html` `map https://localhost:8081/10 https://httpbin.org/html` When connecting to `https://localhost:8081/10`, ATS will first replace `https://localhost:8081/1` with `https://httpbin.org/html`, and then append the `0` to the end. So your final URI will look like: `https://httpbin.org/html0` If two remaps are explicitly specified, both should work. > Incorrect behavior with remap prefix matching > - > > Key: TS-4022 > URL: https://issues.apache.org/jira/browse/TS-4022 > Project: Traffic Server > Issue Type: Bug > Components: Remap API >Reporter: Daniel Xu > > If you have two remap rules like this: > `map https://localhost:8081/1 https://httpbin.org/html` > `map https://localhost:8081/10 https://httpbin.org/html` > When connecting to `https://localhost:8081/10`, ATS will first replace > `https://localhost:8081/1` with `https://httpbin.org/html`, and then append > the `0` to the end. > So your final URI will look like: > `https://httpbin.org/html0` > , which should not be the case. > If two remaps are explicitly specified, both should work. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Assigned] (TS-4021) Lua Plugin - Expose API Call TSHttpTxnFollowRedirect()
[ https://issues.apache.org/jira/browse/TS-4021?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Kit Chan reassigned TS-4021: Assignee: Kit Chan > Lua Plugin - Expose API Call TSHttpTxnFollowRedirect() > -- > > Key: TS-4021 > URL: https://issues.apache.org/jira/browse/TS-4021 > Project: Traffic Server > Issue Type: New Feature >Affects Versions: 6.1.0 >Reporter: Jeremy Payne >Assignee: Kit Chan >Priority: Minor > > Instead of relying on a config override, this plugin 'new feature' would > allow for enabling origin server redirection on the fly; via a direct API > call. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (TS-4021) Lua Plugin - Expose API Call TSHttpTxnFollowRedirect()
[ https://issues.apache.org/jira/browse/TS-4021?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15004417#comment-15004417 ] Kit Chan commented on TS-4021: -- I can take a look over the weekend and the summit to do that. Or if you beat me to that, I can review and merge it in for you. Thanks. Kit > Lua Plugin - Expose API Call TSHttpTxnFollowRedirect() > -- > > Key: TS-4021 > URL: https://issues.apache.org/jira/browse/TS-4021 > Project: Traffic Server > Issue Type: New Feature >Affects Versions: 6.1.0 >Reporter: Jeremy Payne >Assignee: Kit Chan >Priority: Minor > > Instead of relying on a config override, this plugin 'new feature' would > allow for enabling origin server redirection on the fly; via a direct API > call. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (TS-3985) TSHttpTxnCacheLookupStatusSet(HIT_STALE) calls cause a crash
[ https://issues.apache.org/jira/browse/TS-3985?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Leif Hedstrom updated TS-3985: -- Labels: Review (was: ) > TSHttpTxnCacheLookupStatusSet(HIT_STALE) calls cause a crash > > > Key: TS-3985 > URL: https://issues.apache.org/jira/browse/TS-3985 > Project: Traffic Server > Issue Type: Bug > Components: Cache, DNS >Reporter: song > Labels: Review > Fix For: 6.1.0 > > Attachments: untitled.diff > > > Dear > ATS cause a crash in how_to_open_connection while using > TSHttpTxnCacheLookupStatusSet . In Function > HttpTransact::HandleCacheOpenReadHit, the hook pending_work was set to > issue_revalidate function and the variable " s->current.request_to = > ORIGIN_SERVER". But the hook only be released while talking to a parent > proxy in PPDNSLookup function. How to fix it. > thanks -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (TS-4021) Lua Plugin - Expose API Call TSHttpTxnFollowRedirect()
[ https://issues.apache.org/jira/browse/TS-4021?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Kit Chan updated TS-4021: - Component/s: Plugins Lua > Lua Plugin - Expose API Call TSHttpTxnFollowRedirect() > -- > > Key: TS-4021 > URL: https://issues.apache.org/jira/browse/TS-4021 > Project: Traffic Server > Issue Type: New Feature > Components: Lua, Plugins >Affects Versions: 6.1.0 >Reporter: Jeremy Payne >Assignee: Kit Chan >Priority: Minor > > Instead of relying on a config override, this plugin 'new feature' would > allow for enabling origin server redirection on the fly; via a direct API > call. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (TS-4021) Lua Plugin - Expose API Call TSHttpTxnFollowRedirect()
[ https://issues.apache.org/jira/browse/TS-4021?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Kit Chan updated TS-4021: - Fix Version/s: 6.1.0 > Lua Plugin - Expose API Call TSHttpTxnFollowRedirect() > -- > > Key: TS-4021 > URL: https://issues.apache.org/jira/browse/TS-4021 > Project: Traffic Server > Issue Type: New Feature > Components: Lua, Plugins >Affects Versions: 6.1.0 >Reporter: Jeremy Payne >Assignee: Kit Chan >Priority: Minor > Fix For: 6.1.0 > > > Instead of relying on a config override, this plugin 'new feature' would > allow for enabling origin server redirection on the fly; via a direct API > call. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (TS-4022) Incorrect behavior with remap prefix matching
[ https://issues.apache.org/jira/browse/TS-4022?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15004476#comment-15004476 ] Leif Hedstrom commented on TS-4022: --- This is actually as expected. If you want to make sure that the first rule only matches e.g. /1/, you have to anchor it. E.g. map https://localhost:8081/1/ https://httpbin.org/html Does that work and solve your problem? The anchoring was added quite a while ago (prior to Open Source), and might not be properly documented either? > Incorrect behavior with remap prefix matching > - > > Key: TS-4022 > URL: https://issues.apache.org/jira/browse/TS-4022 > Project: Traffic Server > Issue Type: Bug > Components: Remap API >Reporter: Daniel Xu > > If you have two remap rules like this: > `map https://localhost:8081/1 https://httpbin.org/html` > `map https://localhost:8081/10 https://httpbin.org/html` > When connecting to `https://localhost:8081/10`, ATS will first replace > `https://localhost:8081/1` with `https://httpbin.org/html`, and then append > the `0` to the end. > So your final URI will look like: > `https://httpbin.org/html0`, which should not be the case. > If two remaps are explicitly specified, both should work. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (TS-4022) Incorrect behavior with remap prefix matching
[ https://issues.apache.org/jira/browse/TS-4022?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15004668#comment-15004668 ] Leif Hedstrom commented on TS-4022: --- Hmmm, yeah, maybe I didn't read this properly. Yeah, that sounds odd. > Incorrect behavior with remap prefix matching > - > > Key: TS-4022 > URL: https://issues.apache.org/jira/browse/TS-4022 > Project: Traffic Server > Issue Type: Bug > Components: Remap API >Reporter: Daniel Xu > > If you have two remap rules like this: > `map https://localhost:8081/1 https://httpbin.org/html` > `map https://localhost:8081/10 https://httpbin.org/html` > When connecting to `https://localhost:8081/10`, ATS will first replace > `https://localhost:8081/1` with `https://httpbin.org/html`, and then append > the `0` to the end. > So your final URI will look like: > `https://httpbin.org/html0`, which should not be the case. > If two remaps are explicitly specified, both should work. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Issue Comment Deleted] (TS-4022) Incorrect behavior with remap prefix matching
[ https://issues.apache.org/jira/browse/TS-4022?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Leif Hedstrom updated TS-4022: -- Comment: was deleted (was: Hmmm, yeah, maybe I didn't read this properly. Yeah, that sounds odd.) > Incorrect behavior with remap prefix matching > - > > Key: TS-4022 > URL: https://issues.apache.org/jira/browse/TS-4022 > Project: Traffic Server > Issue Type: Bug > Components: Remap API >Reporter: Daniel Xu > > If you have two remap rules like this: > `map https://localhost:8081/1 https://httpbin.org/html` > `map https://localhost:8081/10 https://httpbin.org/html` > When connecting to `https://localhost:8081/10`, ATS will first replace > `https://localhost:8081/1` with `https://httpbin.org/html`, and then append > the `0` to the end. > So your final URI will look like: > `https://httpbin.org/html0`, which should not be the case. > If two remaps are explicitly specified, both should work. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (TS-4022) Incorrect behavior with remap prefix matching
[ https://issues.apache.org/jira/browse/TS-4022?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15004670#comment-15004670 ] Alan M. Carroll commented on TS-4022: - Yes, What Leif describes is the designed behavior. I thought when we talked about this you were getting 404 / Not Found On Accelerator errors with leading digits in the URL path. > Incorrect behavior with remap prefix matching > - > > Key: TS-4022 > URL: https://issues.apache.org/jira/browse/TS-4022 > Project: Traffic Server > Issue Type: Bug > Components: Remap API >Reporter: Daniel Xu > > If you have two remap rules like this: > `map https://localhost:8081/1 https://httpbin.org/html` > `map https://localhost:8081/10 https://httpbin.org/html` > When connecting to `https://localhost:8081/10`, ATS will first replace > `https://localhost:8081/1` with `https://httpbin.org/html`, and then append > the `0` to the end. > So your final URI will look like: > `https://httpbin.org/html0`, which should not be the case. > If two remaps are explicitly specified, both should work. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (TS-4022) Incorrect behavior with remap prefix matching
[ https://issues.apache.org/jira/browse/TS-4022?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15004683#comment-15004683 ] Daniel Xu commented on TS-4022: --- Ok, then I think what I was seeing was expected behavior. To clarify what I previously said about the 404, I realized a little later that the 404s were happening because the remap rules did a greedy substitution and left a bunch of trailing characters in the URI. What I put in the bug description is what had happened to the best of my knowledge. > Incorrect behavior with remap prefix matching > - > > Key: TS-4022 > URL: https://issues.apache.org/jira/browse/TS-4022 > Project: Traffic Server > Issue Type: Bug > Components: Remap API >Reporter: Daniel Xu > > If you have two remap rules like this: > `map https://localhost:8081/1 https://httpbin.org/html` > `map https://localhost:8081/10 https://httpbin.org/html` > When connecting to `https://localhost:8081/10`, ATS will first replace > `https://localhost:8081/1` with `https://httpbin.org/html`, and then append > the `0` to the end. > So your final URI will look like: > `https://httpbin.org/html0`, which should not be the case. > If two remaps are explicitly specified, both should work. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Closed] (TS-4022) Incorrect behavior with remap prefix matching
[ https://issues.apache.org/jira/browse/TS-4022?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Daniel Xu closed TS-4022. - Resolution: Invalid > Incorrect behavior with remap prefix matching > - > > Key: TS-4022 > URL: https://issues.apache.org/jira/browse/TS-4022 > Project: Traffic Server > Issue Type: Bug > Components: Remap API >Reporter: Daniel Xu > > If you have two remap rules like this: > `map https://localhost:8081/1 https://httpbin.org/html` > `map https://localhost:8081/10 https://httpbin.org/html` > When connecting to `https://localhost:8081/10`, ATS will first replace > `https://localhost:8081/1` with `https://httpbin.org/html`, and then append > the `0` to the end. > So your final URI will look like: > `https://httpbin.org/html0`, which should not be the case. > If two remaps are explicitly specified, both should work. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (TS-4021) Lua Plugin - Expose API Call TSHttpTxnFollowRedirect()
[ https://issues.apache.org/jira/browse/TS-4021?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15004702#comment-15004702 ] ASF GitHub Bot commented on TS-4021: GitHub user pbchou opened a pull request: https://github.com/apache/trafficserver/pull/335 For TS-4021, added ts.http.enable_redirect() to the Lua API. This calls the TSHttpTxnFollowRedirect() API function. You can merge this pull request into a Git repository by running: $ git pull https://github.com/pbchou/trafficserver ts4021 Alternatively you can review and apply these changes as the patch at: https://github.com/apache/trafficserver/pull/335.patch To close this pull request, make a commit to your master/trunk branch with (at least) the following in the commit message: This closes #335 commit 75cd7804b6092cb3717151645eb3a45de6d085ee Author: pbchou Date: 2015-11-13T20:51:42Z For TS-4021, added ts.http.enable_redirect() to the Lua API. This calls the TSHttpTxnFollowRedirect() API function. > Lua Plugin - Expose API Call TSHttpTxnFollowRedirect() > -- > > Key: TS-4021 > URL: https://issues.apache.org/jira/browse/TS-4021 > Project: Traffic Server > Issue Type: New Feature > Components: Lua, Plugins >Affects Versions: 6.1.0 >Reporter: Jeremy Payne >Assignee: Kit Chan >Priority: Minor > Fix For: 6.1.0 > > > Instead of relying on a config override, this plugin 'new feature' would > allow for enabling origin server redirection on the fly; via a direct API > call. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (TS-4021) Lua Plugin - Expose API Call TSHttpTxnFollowRedirect()
[ https://issues.apache.org/jira/browse/TS-4021?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15004713#comment-15004713 ] Peter Chou commented on TS-4021: Kit, thanks for volunteering to take a look at the proposed changes. I did basic testing under Ubuntu Linux 32-bit for this change. * First, we left "CONFIG proxy.config.http.redirection_enabled" out of records.config so it stayed as default of 0 or disabled globally. * Second, In remap.config, we added "map ... @plugin=tslua.so @pparam=.../my.lua". * Third, in my.lua we added -- function do_remap() ts.http.enable_redirect(1) return 0 end > Lua Plugin - Expose API Call TSHttpTxnFollowRedirect() > -- > > Key: TS-4021 > URL: https://issues.apache.org/jira/browse/TS-4021 > Project: Traffic Server > Issue Type: New Feature > Components: Lua, Plugins >Affects Versions: 6.1.0 >Reporter: Jeremy Payne >Assignee: Kit Chan >Priority: Minor > Fix For: 6.1.0 > > > Instead of relying on a config override, this plugin 'new feature' would > allow for enabling origin server redirection on the fly; via a direct API > call. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Created] (TS-4023) cachekey_norm plugin
Gancho Tenev created TS-4023: Summary: cachekey_norm plugin Key: TS-4023 URL: https://issues.apache.org/jira/browse/TS-4023 Project: Traffic Server Issue Type: Improvement Components: Cache Reporter: Gancho Tenev This plugin allows some common cache key normalizations of the URI. It can - sort query parameters so reordering can be a cache hit - ignore specific query parameters from the cache key by name or regular expression - ignore all query parameters from the cache key - only use specific query parameters in the cache key by name or regular expression - include headers or cookies by name - capture / replace values from the User-Agent header. - classify request using User-Agent and a list of regular expressions -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (TS-4021) Lua Plugin - Expose API Call TSHttpTxnFollowRedirect()
[ https://issues.apache.org/jira/browse/TS-4021?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15004786#comment-15004786 ] Kit Chan commented on TS-4021: -- Would you mind updating the doc as well? https://github.com/apache/trafficserver/blob/master/doc/admin-guide/plugins/ts_lua.en.rst Thanks. > Lua Plugin - Expose API Call TSHttpTxnFollowRedirect() > -- > > Key: TS-4021 > URL: https://issues.apache.org/jira/browse/TS-4021 > Project: Traffic Server > Issue Type: New Feature > Components: Lua, Plugins >Affects Versions: 6.1.0 >Reporter: Jeremy Payne >Assignee: Kit Chan >Priority: Minor > Fix For: 6.1.0 > > > Instead of relying on a config override, this plugin 'new feature' would > allow for enabling origin server redirection on the fly; via a direct API > call. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (TS-4023) cachekey_norm plugin
[
https://issues.apache.org/jira/browse/TS-4023?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15004787#comment-15004787
]
James Peach commented on TS-4023:
-
Please let's call this plugin {{cachekey}}.
> cachekey_norm plugin
>
>
> Key: TS-4023
> URL: https://issues.apache.org/jira/browse/TS-4023
> Project: Traffic Server
> Issue Type: Improvement
> Components: Cache
>Reporter: Gancho Tenev
>
> This plugin allows some common cache key normalizations of the URI. It can
> - sort query parameters so reordering can be a cache hit
> - ignore specific query parameters from the cache key by name or regular
> expression
> - ignore all query parameters from the cache key
> - only use specific query parameters in the cache key by name or regular
> expression
> - include headers or cookies by name
> - capture / replace values from the User-Agent header.
> - classify request using User-Agent and a list of regular expressions
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Updated] (TS-4023) cachekey_norm plugin
[ https://issues.apache.org/jira/browse/TS-4023?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Leif Hedstrom updated TS-4023: -- Assignee: Gancho Tenev > cachekey_norm plugin > > > Key: TS-4023 > URL: https://issues.apache.org/jira/browse/TS-4023 > Project: Traffic Server > Issue Type: Improvement > Components: Cache >Reporter: Gancho Tenev >Assignee: Gancho Tenev > Fix For: 6.1.0 > > > This plugin allows some common cache key normalizations of the URI. It can > - sort query parameters so reordering can be a cache hit > - ignore specific query parameters from the cache key by name or regular > expression > - ignore all query parameters from the cache key > - only use specific query parameters in the cache key by name or regular > expression > - include headers or cookies by name > - capture / replace values from the User-Agent header. > - classify request using User-Agent and a list of regular expressions -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (TS-4023) cachekey_norm plugin
[ https://issues.apache.org/jira/browse/TS-4023?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Leif Hedstrom updated TS-4023: -- Fix Version/s: 6.1.0 > cachekey_norm plugin > > > Key: TS-4023 > URL: https://issues.apache.org/jira/browse/TS-4023 > Project: Traffic Server > Issue Type: Improvement > Components: Cache >Reporter: Gancho Tenev > Fix For: 6.1.0 > > > This plugin allows some common cache key normalizations of the URI. It can > - sort query parameters so reordering can be a cache hit > - ignore specific query parameters from the cache key by name or regular > expression > - ignore all query parameters from the cache key > - only use specific query parameters in the cache key by name or regular > expression > - include headers or cookies by name > - capture / replace values from the User-Agent header. > - classify request using User-Agent and a list of regular expressions -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (TS-4021) Lua Plugin - Expose API Call TSHttpTxnFollowRedirect()
[ https://issues.apache.org/jira/browse/TS-4021?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15004829#comment-15004829 ] Jeremy Payne commented on TS-4021: -- Yeah.. I'll own the documentation update. Look for it once I complete some cursory testing. > Lua Plugin - Expose API Call TSHttpTxnFollowRedirect() > -- > > Key: TS-4021 > URL: https://issues.apache.org/jira/browse/TS-4021 > Project: Traffic Server > Issue Type: New Feature > Components: Lua, Plugins >Affects Versions: 6.1.0 >Reporter: Jeremy Payne >Assignee: Kit Chan >Priority: Minor > Fix For: 6.1.0 > > > Instead of relying on a config override, this plugin 'new feature' would > allow for enabling origin server redirection on the fly; via a direct API > call. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (TS-4012) tcp_reused log field doesn't work for http2/spdy
[ https://issues.apache.org/jira/browse/TS-4012?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15004862#comment-15004862 ] ASF GitHub Bot commented on TS-4012: GitHub user ericcarlschwartz opened a pull request: https://github.com/apache/trafficserver/pull/336 [TS-4012] tcp_reused log field doesn't work for http2/spdy JIRA: https://issues.apache.org/jira/browse/TS-4012 You can merge this pull request into a Git repository by running: $ git pull https://github.com/ericcarlschwartz/trafficserver ts-4012 Alternatively you can review and apply these changes as the patch at: https://github.com/apache/trafficserver/pull/336.patch To close this pull request, make a commit to your master/trunk branch with (at least) the following in the commit message: This closes #336 commit b2304952f701379e37efd6135c904e34876be95e Author: ericcarlschwartz Date: 2015-11-13T22:59:11Z [TS-4012] tcp_reused log field doesn't work for http2/spdy > tcp_reused log field doesn't work for http2/spdy > > > Key: TS-4012 > URL: https://issues.apache.org/jira/browse/TS-4012 > Project: Traffic Server > Issue Type: Bug > Components: Logging >Reporter: Eric Schwartz >Assignee: Eric Schwartz > Fix For: 6.1.0 > > > This is something we noticed at Yahoo! > Because it uses the HttpClientSession transact_count, the tcp_reused log > field will not properly work for http2 and spdy, where the HttpClientSession > isn't reused. > We need to essentially count the number of initiated streams instead. > We've got a fix that does this for HTTP2. With SPDY eventually dying off, > does it make sense to also submit a change to fix this for SPDY? We have code > to do this as well, but it currently involves an H2 dependency that might be > undesirable. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Created] (TS-4024) wire tracing enhancements
Eric Schwartz created TS-4024: - Summary: wire tracing enhancements Key: TS-4024 URL: https://issues.apache.org/jira/browse/TS-4024 Project: Traffic Server Issue Type: Bug Components: Logging Reporter: Eric Schwartz Some enhancements from Yahoo! to make wire tracing dynamically enable-able and to enhance log messages. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (TS-4024) wire tracing enhancements
[ https://issues.apache.org/jira/browse/TS-4024?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15004871#comment-15004871 ] Eric Schwartz commented on TS-4024: --- Could someone assign this to me? > wire tracing enhancements > - > > Key: TS-4024 > URL: https://issues.apache.org/jira/browse/TS-4024 > Project: Traffic Server > Issue Type: Bug > Components: Logging >Reporter: Eric Schwartz > > Some enhancements from Yahoo! to make wire tracing dynamically enable-able > and to enhance log messages. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Comment Edited] (TS-4024) wire tracing enhancements
[ https://issues.apache.org/jira/browse/TS-4024?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15004871#comment-15004871 ] Eric Schwartz edited comment on TS-4024 at 11/13/15 11:06 PM: -- Could someone assign this to me? Have a patch for discussion. was (Author: es): Could someone assign this to me? > wire tracing enhancements > - > > Key: TS-4024 > URL: https://issues.apache.org/jira/browse/TS-4024 > Project: Traffic Server > Issue Type: Bug > Components: Logging >Reporter: Eric Schwartz > > Some enhancements from Yahoo! to make wire tracing dynamically enable-able > and to enhance log messages. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (TS-4024) wire tracing enhancements
[ https://issues.apache.org/jira/browse/TS-4024?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Leif Hedstrom updated TS-4024: -- Assignee: Eric Schwartz > wire tracing enhancements > - > > Key: TS-4024 > URL: https://issues.apache.org/jira/browse/TS-4024 > Project: Traffic Server > Issue Type: Bug > Components: Logging >Reporter: Eric Schwartz >Assignee: Eric Schwartz > Fix For: 6.1.0 > > > Some enhancements from Yahoo! to make wire tracing dynamically enable-able > and to enhance log messages. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (TS-4024) wire tracing enhancements
[ https://issues.apache.org/jira/browse/TS-4024?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Leif Hedstrom updated TS-4024: -- Fix Version/s: 6.1.0 > wire tracing enhancements > - > > Key: TS-4024 > URL: https://issues.apache.org/jira/browse/TS-4024 > Project: Traffic Server > Issue Type: Bug > Components: Logging >Reporter: Eric Schwartz >Assignee: Eric Schwartz > Fix For: 6.1.0 > > > Some enhancements from Yahoo! to make wire tracing dynamically enable-able > and to enhance log messages. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (TS-4019) Headers passed via HTTP/2 should be validated before passing to FetchSM
[
https://issues.apache.org/jira/browse/TS-4019?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15004958#comment-15004958
]
ASF GitHub Bot commented on TS-4019:
Github user bryancall commented on the pull request:
https://github.com/apache/trafficserver/pull/334#issuecomment-156597223
You don't need to squash. I will use a patch to commit it.
> Headers passed via HTTP/2 should be validated before passing to FetchSM
> ---
>
> Key: TS-4019
> URL: https://issues.apache.org/jira/browse/TS-4019
> Project: Traffic Server
> Issue Type: Bug
> Components: HTTP/2
>Reporter: Masakazu Kitajo
> Fix For: 6.1.0
>
>
> HTTP/2 header fields which contain invalid characters must not be passed to
> an origin server via HTTP/1.1, and it must be treated as a protocol error.
> {quote}
> 10.3. Intermediary Encapsulation Attacks
>The HTTP/2 header field encoding allows the expression of names that
>are not valid field names in the Internet Message Syntax used by
>HTTP/1.1. Requests or responses containing invalid header field
>names MUST be treated as malformed (Section 8.1.2.6). An
>intermediary therefore cannot translate an HTTP/2 request or response
>containing an invalid field name into an HTTP/1.1 message.
>Similarly, HTTP/2 allows header field values that are not valid.
>While most of the values that can be encoded will not alter header
>field parsing, carriage return (CR, ASCII 0xd), line feed (LF, ASCII
>0xa), and the zero character (NUL, ASCII 0x0) might be exploited by
>an attacker if they are translated verbatim. Any request or response
>that contains a character not permitted in a header field value MUST
>be treated as malformed (Section 8.1.2.6). Valid characters are
>defined by the "field-content" ABNF rule in Section 3.2 of \[RFC7230\].
> {quote}
> https://tools.ietf.org/html/rfc7540#section-10.3
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Commented] (TS-4021) Lua Plugin - Expose API Call TSHttpTxnFollowRedirect()
[ https://issues.apache.org/jira/browse/TS-4021?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15004971#comment-15004971 ] ASF GitHub Bot commented on TS-4021: Github user asfgit closed the pull request at: https://github.com/apache/trafficserver/pull/335 > Lua Plugin - Expose API Call TSHttpTxnFollowRedirect() > -- > > Key: TS-4021 > URL: https://issues.apache.org/jira/browse/TS-4021 > Project: Traffic Server > Issue Type: New Feature > Components: Lua, Plugins >Affects Versions: 6.1.0 >Reporter: Jeremy Payne >Assignee: Kit Chan >Priority: Minor > Fix For: 6.1.0 > > > Instead of relying on a config override, this plugin 'new feature' would > allow for enabling origin server redirection on the fly; via a direct API > call. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (TS-4021) Lua Plugin - Expose API Call TSHttpTxnFollowRedirect()
[ https://issues.apache.org/jira/browse/TS-4021?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15004970#comment-15004970 ] ASF subversion and git services commented on TS-4021: - Commit 7b467783da30ef18983ef37068ecd1300f70dcb4 in trafficserver's branch refs/heads/master from [~pbchou] [ https://git-wip-us.apache.org/repos/asf?p=trafficserver.git;h=7b46778 ] TS-4021: TSHttpTxnFollowRedirect() in ts_lua plugin. This closes #335 > Lua Plugin - Expose API Call TSHttpTxnFollowRedirect() > -- > > Key: TS-4021 > URL: https://issues.apache.org/jira/browse/TS-4021 > Project: Traffic Server > Issue Type: New Feature > Components: Lua, Plugins >Affects Versions: 6.1.0 >Reporter: Jeremy Payne >Assignee: Kit Chan >Priority: Minor > Fix For: 6.1.0 > > > Instead of relying on a config override, this plugin 'new feature' would > allow for enabling origin server redirection on the fly; via a direct API > call. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (TS-4021) Lua Plugin - Expose API Call TSHttpTxnFollowRedirect()
[ https://issues.apache.org/jira/browse/TS-4021?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15004973#comment-15004973 ] Kit Chan commented on TS-4021: -- merge the pull request already. I am not closing it yet till the documentation is updated. Will get to write this later or PR is extremely welcome. Thanks. > Lua Plugin - Expose API Call TSHttpTxnFollowRedirect() > -- > > Key: TS-4021 > URL: https://issues.apache.org/jira/browse/TS-4021 > Project: Traffic Server > Issue Type: New Feature > Components: Lua, Plugins >Affects Versions: 6.1.0 >Reporter: Jeremy Payne >Assignee: Kit Chan >Priority: Minor > Fix For: 6.1.0 > > > Instead of relying on a config override, this plugin 'new feature' would > allow for enabling origin server redirection on the fly; via a direct API > call. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (TS-4021) Lua Plugin - Expose API Call TSHttpTxnFollowRedirect()
[ https://issues.apache.org/jira/browse/TS-4021?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15005082#comment-15005082 ] Jeremy Payne commented on TS-4021: -- My testing is complete and will have documentation done by 11-16-2015 > Lua Plugin - Expose API Call TSHttpTxnFollowRedirect() > -- > > Key: TS-4021 > URL: https://issues.apache.org/jira/browse/TS-4021 > Project: Traffic Server > Issue Type: New Feature > Components: Lua, Plugins >Affects Versions: 6.1.0 >Reporter: Jeremy Payne >Assignee: Kit Chan >Priority: Minor > Fix For: 6.1.0 > > > Instead of relying on a config override, this plugin 'new feature' would > allow for enabling origin server redirection on the fly; via a direct API > call. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (TS-4023) cachekey plugin
[ https://issues.apache.org/jira/browse/TS-4023?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Gancho Tenev updated TS-4023: - Summary: cachekey plugin (was: cachekey_norm plugin) > cachekey plugin > --- > > Key: TS-4023 > URL: https://issues.apache.org/jira/browse/TS-4023 > Project: Traffic Server > Issue Type: Improvement > Components: Cache >Reporter: Gancho Tenev >Assignee: Gancho Tenev > Fix For: 6.1.0 > > > This plugin allows some common cache key normalizations of the URI. It can > - sort query parameters so reordering can be a cache hit > - ignore specific query parameters from the cache key by name or regular > expression > - ignore all query parameters from the cache key > - only use specific query parameters in the cache key by name or regular > expression > - include headers or cookies by name > - capture / replace values from the User-Agent header. > - classify request using User-Agent and a list of regular expressions -- This message was sent by Atlassian JIRA (v6.3.4#6332)
