[jira] [Work logged] (TS-4683) header_rewrite: warning if you use a hook that predates "remap" in a remap mode

[ https://issues.apache.org/jira/browse/TS-4683?focusedWorklogId=25795&page=com.atlassian.jira.plugin.system.issuetabpanels:worklog-tabpanel#worklog-25795 ] ASF GitHub Bot logged work on TS-4683: -- Author: ASF GitHub Bot Cre

[GitHub] trafficserver issue #818: TS-4683 Adds better error handling on config probl...

Github user jpeach commented on the issue: https://github.com/apache/trafficserver/pull/818 👍 --- If your project is set up for it, you can reply to this email and have your reply appear on GitHub as well. If your project does not have this feature enabled and wishes so, or if the

[GitHub] trafficserver pull request #818: TS-4683 Adds better error handling on confi...

Github user jpeach commented on a diff in the pull request: https://github.com/apache/trafficserver/pull/818#discussion_r71650582 --- Diff: lib/ts/tests.cc --- @@ -19,7 +19,7 @@ limitations under the License. */ -#include "ts/TestBox.h" +#include "ts/Regres

[jira] [Work logged] (TS-4683) header_rewrite: warning if you use a hook that predates "remap" in a remap mode

[ https://issues.apache.org/jira/browse/TS-4683?focusedWorklogId=25794&page=com.atlassian.jira.plugin.system.issuetabpanels:worklog-tabpanel#worklog-25794 ] ASF GitHub Bot logged work on TS-4683: -- Author: ASF GitHub Bot Cre

[jira] [Work logged] (TS-4680) Not thread safe initialization in TS*DirGet() functions

[ https://issues.apache.org/jira/browse/TS-4680?focusedWorklogId=25793&page=com.atlassian.jira.plugin.system.issuetabpanels:worklog-tabpanel#worklog-25793 ] ASF GitHub Bot logged work on TS-4680: -- Author: ASF GitHub Bot Cre

[GitHub] trafficserver issue #815: TS-4680: thread safe initialization in TS*DirGet()...

Github user jpeach commented on the issue: https://github.com/apache/trafficserver/pull/815 👍 --- If your project is set up for it, you can reply to this email and have your reply appear on GitHub as well. If your project does not have this feature enabled and wishes so, or if the

[GitHub] trafficserver pull request #819: TS-4311 Removes support for SPDY completely

Github user jpeach commented on a diff in the pull request: https://github.com/apache/trafficserver/pull/819#discussion_r71649770 --- Diff: lib/ts/ink_config.h.in --- @@ -127,5 +127,6 @@ #define TS_BUILD_CANONICAL_HOST "@host@" #define TS_BUILD_DEFAULT_LOOPBACK_IFACE

[jira] [Work logged] (TS-4311) Remove SPDY protocol support

[ https://issues.apache.org/jira/browse/TS-4311?focusedWorklogId=25792&page=com.atlassian.jira.plugin.system.issuetabpanels:worklog-tabpanel#worklog-25792 ] ASF GitHub Bot logged work on TS-4311: -- Author: ASF GitHub Bot Cre

[jira] [Commented] (TS-2987) TS API to identify if the client connection is via HTTP/2

[ https://issues.apache.org/jira/browse/TS-2987?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15387164#comment-15387164 ] James Peach commented on TS-2987: - If you look in the git history we used to have a "protocol

[jira] [Work logged] (TS-4072) Diagnostic log rolling races

[ https://issues.apache.org/jira/browse/TS-4072?focusedWorklogId=25791&page=com.atlassian.jira.plugin.system.issuetabpanels:worklog-tabpanel#worklog-25791 ] ASF GitHub Bot logged work on TS-4072: -- Author: ASF GitHub Bot Cre

[GitHub] trafficserver issue #568: TS-4072 Diagnostic log rolling races

Github user danobi commented on the issue: https://github.com/apache/trafficserver/pull/568 @zwoop clang-formatted & rebased --- If your project is set up for it, you can reply to this email and have your reply appear on GitHub as well. If your project does not have this feature enabl

[jira] [Updated] (TS-3474) HTTP/2 Server Push support in ATS

[ https://issues.apache.org/jira/browse/TS-3474?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Masakazu Kitajo updated TS-3474: Fix Version/s: (was: sometime) 7.0.0 > HTTP/2 Server Push support in ATS > -

[jira] [Commented] (TS-3474) HTTP/2 Server Push support in ATS

[ https://issues.apache.org/jira/browse/TS-3474?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15387068#comment-15387068 ] Masakazu Kitajo commented on TS-3474: - I'm going to send a pull request by the end of thi

[jira] [Assigned] (TS-3474) HTTP/2 Server Push support in ATS

[ https://issues.apache.org/jira/browse/TS-3474?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Masakazu Kitajo reassigned TS-3474: --- Assignee: Masakazu Kitajo > HTTP/2 Server Push support in ATS >

[jira] [Updated] (TS-2987) TS API to identify if the client connection is via HTTP/2

[ https://issues.apache.org/jira/browse/TS-2987?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Masaori Koshiba updated TS-2987: Fix Version/s: 7.0.0 > TS API to identify if the client connection is via HTTP/2 >

Jenkins build is back to normal : centos_7-master » gcc,centos_7,debug #1861

See

[jira] [Commented] (TS-2987) TS API to identify if the client connection is via HTTP/2

[ https://issues.apache.org/jira/browse/TS-2987?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15387022#comment-15387022 ] Masaori Koshiba commented on TS-2987: - I agree. Tracking protocols using {{plugin_tag}} i

[jira] [Comment Edited] (TS-2987) TS API to identify if the client connection is via HTTP/2

[ https://issues.apache.org/jira/browse/TS-2987?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15387022#comment-15387022 ] Masaori Koshiba edited comment on TS-2987 at 7/21/16 2:20 AM: -- I

Jenkins build is back to normal : osx-master » clang,osx,debug #1039

See

[jira] [Work logged] (TS-4622) Ports from SRV lookups aren't used

[ https://issues.apache.org/jira/browse/TS-4622?focusedWorklogId=25790&page=com.atlassian.jira.plugin.system.issuetabpanels:worklog-tabpanel#worklog-25790 ] ASF GitHub Bot logged work on TS-4622: -- Author: ASF GitHub Bot Cre

[GitHub] trafficserver issue #773: TS-4622 Use port from SRV response when connecting...

Github user atsci commented on the issue: https://github.com/apache/trafficserver/pull/773 FreeBSD build *successful*! See https://ci.trafficserver.apache.org/job/Github-FreeBSD/465/ for details. --- If your project is set up for it, you can reply to this email and have your r

[GitHub] trafficserver issue #773: TS-4622 Use port from SRV response when connecting...

Github user atsci commented on the issue: https://github.com/apache/trafficserver/pull/773 Linux build *successful*! See https://ci.trafficserver.apache.org/job/Github-Linux/360/ for details. --- If your project is set up for it, you can reply to this email and have your reply

[jira] [Work logged] (TS-4622) Ports from SRV lookups aren't used

[ https://issues.apache.org/jira/browse/TS-4622?focusedWorklogId=25789&page=com.atlassian.jira.plugin.system.issuetabpanels:worklog-tabpanel#worklog-25789 ] ASF GitHub Bot logged work on TS-4622: -- Author: ASF GitHub Bot Cre

[jira] [Work logged] (TS-4622) Ports from SRV lookups aren't used

[ https://issues.apache.org/jira/browse/TS-4622?focusedWorklogId=25788&page=com.atlassian.jira.plugin.system.issuetabpanels:worklog-tabpanel#worklog-25788 ] ASF GitHub Bot logged work on TS-4622: -- Author: ASF GitHub Bot Cre

[GitHub] trafficserver issue #773: TS-4622 Use port from SRV response when connecting...

Github user atsci commented on the issue: https://github.com/apache/trafficserver/pull/773 FreeBSD build *successful*! See https://ci.trafficserver.apache.org/job/Github-FreeBSD/464/ for details. --- If your project is set up for it, you can reply to this email and have your r

[jira] [Resolved] (TS-4639) Add git to vagrant builds

[ https://issues.apache.org/jira/browse/TS-4639?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] James Peach resolved TS-4639. - Resolution: Fixed > Add git to vagrant builds > - > > Key: TS-4639 >

[GitHub] trafficserver pull request #816: TS-4639: Add git to Vagrant builds

Github user jpeach closed the pull request at: https://github.com/apache/trafficserver/pull/816 --- If your project is set up for it, you can reply to this email and have your reply appear on GitHub as well. If your project does not have this feature enabled and wishes so, or if the feature

[jira] [Work logged] (TS-4639) Add git to vagrant builds

[ https://issues.apache.org/jira/browse/TS-4639?focusedWorklogId=25787&page=com.atlassian.jira.plugin.system.issuetabpanels:worklog-tabpanel#worklog-25787 ] ASF GitHub Bot logged work on TS-4639: -- Author: ASF GitHub Bot Cre

[jira] [Work logged] (TS-4622) Ports from SRV lookups aren't used

[ https://issues.apache.org/jira/browse/TS-4622?focusedWorklogId=25786&page=com.atlassian.jira.plugin.system.issuetabpanels:worklog-tabpanel#worklog-25786 ] ASF GitHub Bot logged work on TS-4622: -- Author: ASF GitHub Bot Cre

[GitHub] trafficserver issue #773: TS-4622 Use port from SRV response when connecting...

Github user jpeach commented on the issue: https://github.com/apache/trafficserver/pull/773 👍 This looks good to me and I think it will be safe w/ "TsHttpTxnServerAddrSet()". --- If your project is set up for it, you can reply to this email and have your reply appear on GitHub as

[jira] [Updated] (TS-2987) TS API to identify if the client connection is via HTTP/2

[ https://issues.apache.org/jira/browse/TS-2987?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Kit Chan updated TS-2987: - Component/s: (was: SPDY) (was: Plugins) TS API HTTP/2 > TS

[jira] [Commented] (TS-2987) TS API to identify if the client connection is via HTTP/2

[ https://issues.apache.org/jira/browse/TS-2987?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15386971#comment-15386971 ] Kit Chan commented on TS-2987: -- I think [~sudheerv] originally has a patch to use plugin_tag for

[jira] [Commented] (TS-2987) TS API to identify if the client connection is via HTTP/2

[ https://issues.apache.org/jira/browse/TS-2987?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15386970#comment-15386970 ] James Peach commented on TS-2987: - Yes, but let's try not to couple this to plugins. > TS AP

[jira] [Commented] (TS-2987) TS API to identify if the client connection is via HTTP/2

[ https://issues.apache.org/jira/browse/TS-2987?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15386966#comment-15386966 ] Kit Chan commented on TS-2987: -- Reopening since I think we still need an API for us to identify

[jira] [Reopened] (TS-2987) TS API to identify if the client connection is via HTTP/2

[ https://issues.apache.org/jira/browse/TS-2987?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Kit Chan reopened TS-2987: -- > TS API to identify if the client connection is via HTTP/2 > -

[jira] [Updated] (TS-2987) TS API to identify if the client connection is via HTTP/2

[ https://issues.apache.org/jira/browse/TS-2987?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Kit Chan updated TS-2987: - Summary: TS API to identify if the client connection is via HTTP/2 (was: TS API to identify if the client connection

[jira] [Work logged] (TS-4311) Remove SPDY protocol support

[ https://issues.apache.org/jira/browse/TS-4311?focusedWorklogId=25785&page=com.atlassian.jira.plugin.system.issuetabpanels:worklog-tabpanel#worklog-25785 ] ASF GitHub Bot logged work on TS-4311: -- Author: ASF GitHub Bot Cre

[GitHub] trafficserver issue #819: TS-4311 Removes support for SPDY completely

Github user atsci commented on the issue: https://github.com/apache/trafficserver/pull/819 Linux build *successful*! See https://ci.trafficserver.apache.org/job/Github-Linux/359/ for details. --- If your project is set up for it, you can reply to this email and have your reply

[jira] [Work logged] (TS-4311) Remove SPDY protocol support

[ https://issues.apache.org/jira/browse/TS-4311?focusedWorklogId=25784&page=com.atlassian.jira.plugin.system.issuetabpanels:worklog-tabpanel#worklog-25784 ] ASF GitHub Bot logged work on TS-4311: -- Author: ASF GitHub Bot Cre

[GitHub] trafficserver issue #819: TS-4311 Removes support for SPDY completely

Github user atsci commented on the issue: https://github.com/apache/trafficserver/pull/819 FreeBSD build *successful*! See https://ci.trafficserver.apache.org/job/Github-FreeBSD/463/ for details. --- If your project is set up for it, you can reply to this email and have your r

[GitHub] trafficserver pull request #819: TS-4311 Removes support for SPDY completely

GitHub user zwoop opened a pull request: https://github.com/apache/trafficserver/pull/819 TS-4311 Removes support for SPDY completely You can merge this pull request into a Git repository by running: $ git pull https://github.com/zwoop/trafficserver TS-4311 Alternatively you

[jira] [Work logged] (TS-4311) Remove SPDY protocol support

[ https://issues.apache.org/jira/browse/TS-4311?focusedWorklogId=25783&page=com.atlassian.jira.plugin.system.issuetabpanels:worklog-tabpanel#worklog-25783 ] ASF GitHub Bot logged work on TS-4311: -- Author: ASF GitHub Bot Cre

Build failed in Jenkins: centos_7-master » gcc,centos_7,debug #1860

See -- [...truncated 18076 lines...] 0|0|250.74.6.0|250.74.6.0|per_ip| |F|0|0|1970/01/01 00:00:00|3435544084056601407|0|0|1|0 0|0|33.228.1.0|33.228.1.0|p

Build failed in Jenkins: osx-master » clang,osx,debug #1038

See Changes: [Leif Hedstrom] TS-4667 Uses the WKS in the gzip plugin -- [...truncated 2320 lines...] libtool: install: /usr/bin/install -c .libs/collapse

[jira] [Work logged] (TS-4667) The gzip plugin uses non-WKS strings where it should

[ https://issues.apache.org/jira/browse/TS-4667?focusedWorklogId=25782&page=com.atlassian.jira.plugin.system.issuetabpanels:worklog-tabpanel#worklog-25782 ] ASF GitHub Bot logged work on TS-4667: -- Author: ASF GitHub Bot Cre

[GitHub] trafficserver pull request #817: TS-4667 Uses the WKS in the gzip plugin

Github user zwoop closed the pull request at: https://github.com/apache/trafficserver/pull/817 --- If your project is set up for it, you can reply to this email and have your reply appear on GitHub as well. If your project does not have this feature enabled and wishes so, or if the feature i

[jira] [Work logged] (TS-4667) The gzip plugin uses non-WKS strings where it should

[ https://issues.apache.org/jira/browse/TS-4667?focusedWorklogId=25781&page=com.atlassian.jira.plugin.system.issuetabpanels:worklog-tabpanel#worklog-25781 ] ASF GitHub Bot logged work on TS-4667: -- Author: ASF GitHub Bot Cre

[GitHub] trafficserver issue #817: TS-4667 Uses the WKS in the gzip plugin

Github user jpeach commented on the issue: https://github.com/apache/trafficserver/pull/817 👍 --- If your project is set up for it, you can reply to this email and have your reply appear on GitHub as well. If your project does not have this feature enabled and wishes so, or if the

[jira] [Work logged] (TS-4291) Custom log field {{pqhl}} should not count internal headers.

[ https://issues.apache.org/jira/browse/TS-4291?focusedWorklogId=25777&page=com.atlassian.jira.plugin.system.issuetabpanels:worklog-tabpanel#worklog-25777 ] ASF GitHub Bot logged work on TS-4291: -- Author: ASF GitHub Bot Cre

[GitHub] trafficserver issue #588: TS-4291 Adds log field "pqnhl" which ignores inter...

Github user zwoop commented on the issue: https://github.com/apache/trafficserver/pull/588 So, now that we're on the 7.0.0 release cycle, I wonder if we should have pqhl, cqhl, pshl, and sshl all exclude any @ headers? If not, if we really want this, don't we also want all 4 variants

[GitHub] trafficserver pull request #310: TS-3978: Allow empty document caching to fo...

Github user zwoop closed the pull request at: https://github.com/apache/trafficserver/pull/310 --- If your project is set up for it, you can reply to this email and have your reply appear on GitHub as well. If your project does not have this feature enabled and wishes so, or if the feature i

[jira] [Work logged] (TS-4072) Diagnostic log rolling races

[ https://issues.apache.org/jira/browse/TS-4072?focusedWorklogId=25776&page=com.atlassian.jira.plugin.system.issuetabpanels:worklog-tabpanel#worklog-25776 ] ASF GitHub Bot logged work on TS-4072: -- Author: ASF GitHub Bot Cre

[GitHub] trafficserver issue #568: TS-4072 Diagnostic log rolling races

Github user zwoop commented on the issue: https://github.com/apache/trafficserver/pull/568 Well, this slipped through the net. @danobi Can you please make an update to the PR, that does not have merge conflicts? --- If your project is set up for it, you can reply to this email and h

[jira] [Work logged] (TS-3978) Allow empty document caching to follow normal logic

[ https://issues.apache.org/jira/browse/TS-3978?focusedWorklogId=25775&page=com.atlassian.jira.plugin.system.issuetabpanels:worklog-tabpanel#worklog-25775 ] ASF GitHub Bot logged work on TS-3978: -- Author: ASF GitHub Bot Cre

[jira] [Work logged] (TS-3978) Allow empty document caching to follow normal logic

[ https://issues.apache.org/jira/browse/TS-3978?focusedWorklogId=25774&page=com.atlassian.jira.plugin.system.issuetabpanels:worklog-tabpanel#worklog-25774 ] ASF GitHub Bot logged work on TS-3978: -- Author: ASF GitHub Bot Cre

[GitHub] trafficserver issue #310: TS-3978: Allow empty document caching to follow no...

Github user zwoop commented on the issue: https://github.com/apache/trafficserver/pull/310 I'm going to close this for now, please open a new PR after we discuss this more? --- If your project is set up for it, you can reply to this email and have your reply appear on GitHub as well.

[jira] [Work logged] (TS-4680) Not thread safe initialization in TS*DirGet() functions

[ https://issues.apache.org/jira/browse/TS-4680?focusedWorklogId=25773&page=com.atlassian.jira.plugin.system.issuetabpanels:worklog-tabpanel#worklog-25773 ] ASF GitHub Bot logged work on TS-4680: -- Author: ASF GitHub Bot Cre

[GitHub] trafficserver issue #815: TS-4680: thread safe initialization in TS*DirGet()...

Github user atsci commented on the issue: https://github.com/apache/trafficserver/pull/815 Linux build *successful*! See https://ci.trafficserver.apache.org/job/Github-Linux/358/ for details. --- If your project is set up for it, you can reply to this email and have your reply

[jira] [Work logged] (TS-4680) Not thread safe initialization in TS*DirGet() functions

[ https://issues.apache.org/jira/browse/TS-4680?focusedWorklogId=25772&page=com.atlassian.jira.plugin.system.issuetabpanels:worklog-tabpanel#worklog-25772 ] ASF GitHub Bot logged work on TS-4680: -- Author: ASF GitHub Bot Cre

[GitHub] trafficserver issue #815: TS-4680: thread safe initialization in TS*DirGet()...

Github user atsci commented on the issue: https://github.com/apache/trafficserver/pull/815 FreeBSD build *successful*! See https://ci.trafficserver.apache.org/job/Github-FreeBSD/462/ for details. --- If your project is set up for it, you can reply to this email and have your r

[jira] [Work logged] (TS-4680) Not thread safe initialization in TS*DirGet() functions

[ https://issues.apache.org/jira/browse/TS-4680?focusedWorklogId=25771&page=com.atlassian.jira.plugin.system.issuetabpanels:worklog-tabpanel#worklog-25771 ] ASF GitHub Bot logged work on TS-4680: -- Author: ASF GitHub Bot Cre

[GitHub] trafficserver issue #815: TS-4680: thread safe initialization in TS*DirGet()...

Github user zwoop commented on the issue: https://github.com/apache/trafficserver/pull/815 Yeah, like that. Makes you wonder why TSPluginDirGet() was so different though ... I've had issues before with these APIs, where transfer of ownership was not clear. I'll take a peek in a bit.

[jira] [Commented] (TS-2987) TS API to identify if the client connection is via SPDY

[ https://issues.apache.org/jira/browse/TS-2987?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15386549#comment-15386549 ] Leif Hedstrom commented on TS-2987: --- [~kichan] Should we reopen it? If you do, maybe reword

[jira] [Work logged] (TS-4667) The gzip plugin uses non-WKS strings where it should

[ https://issues.apache.org/jira/browse/TS-4667?focusedWorklogId=25770&page=com.atlassian.jira.plugin.system.issuetabpanels:worklog-tabpanel#worklog-25770 ] ASF GitHub Bot logged work on TS-4667: -- Author: ASF GitHub Bot Cre

[GitHub] trafficserver issue #817: TS-4667 Uses the WKS in the gzip plugin

Github user zwoop commented on the issue: https://github.com/apache/trafficserver/pull/817 @oschaaf please review. --- If your project is set up for it, you can reply to this email and have your reply appear on GitHub as well. If your project does not have this feature enabled and wi

[jira] [Work logged] (TS-4639) Add git to vagrant builds

[ https://issues.apache.org/jira/browse/TS-4639?focusedWorklogId=25769&page=com.atlassian.jira.plugin.system.issuetabpanels:worklog-tabpanel#worklog-25769 ] ASF GitHub Bot logged work on TS-4639: -- Author: ASF GitHub Bot Cre

[GitHub] trafficserver issue #816: TS-4639: Add git to Vagrant builds

Github user zwoop commented on the issue: https://github.com/apache/trafficserver/pull/816 I don't speak Vagrant, but this seems reasonable to me. --- If your project is set up for it, you can reply to this email and have your reply appear on GitHub as well. If your project does not h

[jira] [Work logged] (TS-4683) header_rewrite: warning if you use a hook that predates "remap" in a remap mode

[ https://issues.apache.org/jira/browse/TS-4683?focusedWorklogId=25768&page=com.atlassian.jira.plugin.system.issuetabpanels:worklog-tabpanel#worklog-25768 ] ASF GitHub Bot logged work on TS-4683: -- Author: ASF GitHub Bot Cre

[GitHub] trafficserver issue #818: TS-4683 Adds better error handling on config probl...

Github user atsci commented on the issue: https://github.com/apache/trafficserver/pull/818 Linux build *successful*! See https://ci.trafficserver.apache.org/job/Github-Linux/357/ for details. --- If your project is set up for it, you can reply to this email and have your reply

[jira] [Work logged] (TS-4683) header_rewrite: warning if you use a hook that predates "remap" in a remap mode

[ https://issues.apache.org/jira/browse/TS-4683?focusedWorklogId=25767&page=com.atlassian.jira.plugin.system.issuetabpanels:worklog-tabpanel#worklog-25767 ] ASF GitHub Bot logged work on TS-4683: -- Author: ASF GitHub Bot Cre

[GitHub] trafficserver issue #818: TS-4683 Adds better error handling on config probl...

Github user atsci commented on the issue: https://github.com/apache/trafficserver/pull/818 FreeBSD build *successful*! See https://ci.trafficserver.apache.org/job/Github-FreeBSD/461/ for details. --- If your project is set up for it, you can reply to this email and have your r

[jira] [Work logged] (TS-4683) header_rewrite: warning if you use a hook that predates "remap" in a remap mode

[ https://issues.apache.org/jira/browse/TS-4683?focusedWorklogId=25766&page=com.atlassian.jira.plugin.system.issuetabpanels:worklog-tabpanel#worklog-25766 ] ASF GitHub Bot logged work on TS-4683: -- Author: ASF GitHub Bot Cre

[GitHub] trafficserver issue #818: TS-4683 Adds better error handling on config probl...

Github user atsci commented on the issue: https://github.com/apache/trafficserver/pull/818 Linux build *failed*! See https://ci.trafficserver.apache.org/job/Github-Linux/356/ for details. --- If your project is set up for it, you can reply to this email and have your reply app

[jira] [Work logged] (TS-4683) header_rewrite: warning if you use a hook that predates "remap" in a remap mode

[ https://issues.apache.org/jira/browse/TS-4683?focusedWorklogId=25765&page=com.atlassian.jira.plugin.system.issuetabpanels:worklog-tabpanel#worklog-25765 ] ASF GitHub Bot logged work on TS-4683: -- Author: ASF GitHub Bot Cre

[GitHub] trafficserver issue #818: TS-4683 Adds better error handling on config probl...

Github user atsci commented on the issue: https://github.com/apache/trafficserver/pull/818 FreeBSD build *failed*! See https://ci.trafficserver.apache.org/job/Github-FreeBSD/460/ for details. --- If your project is set up for it, you can reply to this email and have your reply

[jira] [Work logged] (TS-4683) header_rewrite: warning if you use a hook that predates "remap" in a remap mode

[ https://issues.apache.org/jira/browse/TS-4683?focusedWorklogId=25764&page=com.atlassian.jira.plugin.system.issuetabpanels:worklog-tabpanel#worklog-25764 ] ASF GitHub Bot logged work on TS-4683: -- Author: ASF GitHub Bot Cre

[GitHub] trafficserver pull request #818: TS-4683 Adds better error handling on confi...

GitHub user zwoop opened a pull request: https://github.com/apache/trafficserver/pull/818 TS-4683 Adds better error handling on config problems You can merge this pull request into a Git repository by running: $ git pull https://github.com/zwoop/trafficserver TS-4683 Alternat

[GitHub] trafficserver issue #817: TS-4667 Uses the WKS in the gzip plugin

Github user atsci commented on the issue: https://github.com/apache/trafficserver/pull/817 Linux build *successful*! See https://ci.trafficserver.apache.org/job/Github-Linux/355/ for details. --- If your project is set up for it, you can reply to this email and have your reply

[jira] [Work logged] (TS-4667) The gzip plugin uses non-WKS strings where it should

[ https://issues.apache.org/jira/browse/TS-4667?focusedWorklogId=25763&page=com.atlassian.jira.plugin.system.issuetabpanels:worklog-tabpanel#worklog-25763 ] ASF GitHub Bot logged work on TS-4667: -- Author: ASF GitHub Bot Cre

[jira] [Work logged] (TS-4667) The gzip plugin uses non-WKS strings where it should

[ https://issues.apache.org/jira/browse/TS-4667?focusedWorklogId=25762&page=com.atlassian.jira.plugin.system.issuetabpanels:worklog-tabpanel#worklog-25762 ] ASF GitHub Bot logged work on TS-4667: -- Author: ASF GitHub Bot Cre

[GitHub] trafficserver issue #817: TS-4667 Uses the WKS in the gzip plugin

Github user atsci commented on the issue: https://github.com/apache/trafficserver/pull/817 FreeBSD build *successful*! See https://ci.trafficserver.apache.org/job/Github-FreeBSD/459/ for details. --- If your project is set up for it, you can reply to this email and have your r

[jira] [Work logged] (TS-4667) The gzip plugin uses non-WKS strings where it should

[ https://issues.apache.org/jira/browse/TS-4667?focusedWorklogId=25761&page=com.atlassian.jira.plugin.system.issuetabpanels:worklog-tabpanel#worklog-25761 ] ASF GitHub Bot logged work on TS-4667: -- Author: ASF GitHub Bot Cre

[GitHub] trafficserver pull request #817: TS-4667 Uses the WKS in the gzip plugin

GitHub user zwoop opened a pull request: https://github.com/apache/trafficserver/pull/817 TS-4667 Uses the WKS in the gzip plugin Instead of just using strings, like "deflate". Albeit, it's functionally the same, this is a bad pattern that we should discourage (using the WKS's cons

[GitHub] trafficserver pull request #816: TS-4639: Add git to Vagrant builds

GitHub user strotyl opened a pull request: https://github.com/apache/trafficserver/pull/816 TS-4639: Add git to Vagrant builds You can merge this pull request into a Git repository by running: $ git pull https://github.com/strotyl/trafficserver TS-4639 Alternatively you can r

[jira] [Work logged] (TS-4639) Add git to vagrant builds

[ https://issues.apache.org/jira/browse/TS-4639?focusedWorklogId=25760&page=com.atlassian.jira.plugin.system.issuetabpanels:worklog-tabpanel#worklog-25760 ] ASF GitHub Bot logged work on TS-4639: -- Author: ASF GitHub Bot Cre

[GitHub] trafficserver pull request #812: TS-4688 handle DNS compression labels in SR...

Github user jacksontj commented on a diff in the pull request: https://github.com/apache/trafficserver/pull/812#discussion_r71542146 --- Diff: iocore/dns/DNS.cc --- @@ -1514,24 +1514,24 @@ dns_process(DNSHandler *handler, HostEnt *buf, int len) cp += dn_skipname(cp, eo

[jira] [Work logged] (TS-4688) DNS resolver doesn't handle DNS compression labels for SRV responses

[ https://issues.apache.org/jira/browse/TS-4688?focusedWorklogId=25758&page=com.atlassian.jira.plugin.system.issuetabpanels:worklog-tabpanel#worklog-25758 ] ASF GitHub Bot logged work on TS-4688: -- Author: ASF GitHub Bot Cre

[jira] [Work logged] (TS-4622) Ports from SRV lookups aren't used

[ https://issues.apache.org/jira/browse/TS-4622?focusedWorklogId=25757&page=com.atlassian.jira.plugin.system.issuetabpanels:worklog-tabpanel#worklog-25757 ] ASF GitHub Bot logged work on TS-4622: -- Author: ASF GitHub Bot Cre

[GitHub] trafficserver issue #773: TS-4622 Use port from SRV response when connecting...

Github user jacksontj commented on the issue: https://github.com/apache/trafficserver/pull/773 @jpeach I did some testing of my own and I can't reproduce any problems with `TsHttpTxnServerAddrSet()` at all. TSHttpTxnServerAddrSet() is supposed to be called before the DNS loo

[jira] [Work logged] (TS-4622) Ports from SRV lookups aren't used

[ https://issues.apache.org/jira/browse/TS-4622?focusedWorklogId=25756&page=com.atlassian.jira.plugin.system.issuetabpanels:worklog-tabpanel#worklog-25756 ] ASF GitHub Bot logged work on TS-4622: -- Author: ASF GitHub Bot Cre

[GitHub] trafficserver issue #773: TS-4622 Use port from SRV response when connecting...

Github user atsci commented on the issue: https://github.com/apache/trafficserver/pull/773 Linux build *successful*! See https://ci.trafficserver.apache.org/job/Github-Linux/354/ for details. --- If your project is set up for it, you can reply to this email and have your reply

[GitHub] trafficserver issue #773: TS-4622 Use port from SRV response when connecting...

Github user atsci commented on the issue: https://github.com/apache/trafficserver/pull/773 FreeBSD build *successful*! See https://ci.trafficserver.apache.org/job/Github-FreeBSD/458/ for details. --- If your project is set up for it, you can reply to this email and have your r

[jira] [Work logged] (TS-4622) Ports from SRV lookups aren't used

[ https://issues.apache.org/jira/browse/TS-4622?focusedWorklogId=25755&page=com.atlassian.jira.plugin.system.issuetabpanels:worklog-tabpanel#worklog-25755 ] ASF GitHub Bot logged work on TS-4622: -- Author: ASF GitHub Bot Cre

[jira] [Work logged] (TS-4622) Ports from SRV lookups aren't used

[ https://issues.apache.org/jira/browse/TS-4622?focusedWorklogId=25754&page=com.atlassian.jira.plugin.system.issuetabpanels:worklog-tabpanel#worklog-25754 ] ASF GitHub Bot logged work on TS-4622: -- Author: ASF GitHub Bot Cre

[GitHub] trafficserver pull request #773: TS-4622 Use port from SRV response when con...

Github user jacksontj commented on a diff in the pull request: https://github.com/apache/trafficserver/pull/773#discussion_r71536060 --- Diff: proxy/http/HttpTransact.cc --- @@ -1783,7 +1783,13 @@ HttpTransact::OSDNSLookup(State *s) // update some state variables with hostdb

[jira] [Resolved] (TS-4653) ESI plugin - $HTTP_COOKIE can leak important cookie info unintentionally

[ https://issues.apache.org/jira/browse/TS-4653?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Kit Chan resolved TS-4653. -- Resolution: Fixed > ESI plugin - $HTTP_COOKIE can leak important cookie info unintentionally >

[jira] [Work logged] (TS-4653) ESI plugin - $HTTP_COOKIE can leak important cookie info unintentionally

[ https://issues.apache.org/jira/browse/TS-4653?focusedWorklogId=25753&page=com.atlassian.jira.plugin.system.issuetabpanels:worklog-tabpanel#worklog-25753 ] ASF GitHub Bot logged work on TS-4653: -- Author: ASF GitHub Bot Cre

[GitHub] trafficserver issue #798: TS-4653: esi plugin - disable HTTP_COOKIE variable...

Github user atsci commented on the issue: https://github.com/apache/trafficserver/pull/798 Linux build *successful*! See https://ci.trafficserver.apache.org/job/Github-Linux/352/ for details. --- If your project is set up for it, you can reply to this email and have your reply

[jira] [Work logged] (TS-4653) ESI plugin - $HTTP_COOKIE can leak important cookie info unintentionally

[ https://issues.apache.org/jira/browse/TS-4653?focusedWorklogId=25752&page=com.atlassian.jira.plugin.system.issuetabpanels:worklog-tabpanel#worklog-25752 ] ASF GitHub Bot logged work on TS-4653: -- Author: ASF GitHub Bot Cre

[GitHub] trafficserver issue #798: TS-4653: esi plugin - disable HTTP_COOKIE variable...

Github user atsci commented on the issue: https://github.com/apache/trafficserver/pull/798 FreeBSD build *successful*! See https://ci.trafficserver.apache.org/job/Github-FreeBSD/457/ for details. --- If your project is set up for it, you can reply to this email and have your r

  1   2   >