Github user oknet commented on the issue:
https://github.com/apache/trafficserver/issues/1412
PR#1583 merged to fix the issue.
---
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
Github user oknet closed the pull request at:
https://github.com/apache/trafficserver/pull/1583
---
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
Github user zizhong commented on the issue:
https://github.com/apache/trafficserver/pull/1609
@bgaff yep, it's pretty fast. Tested on a PROD box. It is around 1ms.
---
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
Github user atsci commented on the issue:
https://github.com/apache/trafficserver/pull/1620
clang-analyzer build *successful*!
https://ci.trafficserver.apache.org/job/clang-analyzer-github/379/
---
If your project is set up for it, you can reply to this email and have your
Github user zwoop commented on the issue:
https://github.com/apache/trafficserver/pull/1612
Cherry picked to 7.1.x
---
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
Github user atsci commented on the issue:
https://github.com/apache/trafficserver/pull/1620
Intel CC build *successful*!
https://ci.trafficserver.apache.org/job/icc-github/247/
---
If your project is set up for it, you can reply to this email and have your
reply appear on
Github user atsci commented on the issue:
https://github.com/apache/trafficserver/pull/1620
Linux build *successful*!
https://ci.trafficserver.apache.org/job/linux-github/1708/
---
If your project is set up for it, you can reply to this email and have your
reply appear on
Github user atsci commented on the issue:
https://github.com/apache/trafficserver/pull/1620
FreeBSD11 build *successful*!
https://ci.trafficserver.apache.org/job/freebsd-github/1817/
---
If your project is set up for it, you can reply to this email and have your
reply appear
Github user atsci commented on the issue:
https://github.com/apache/trafficserver/pull/1620
AU check *successful*!
https://ci.trafficserver.apache.org/job/autest-github/118/
---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub
Github user zwoop commented on the issue:
https://github.com/apache/trafficserver/pull/1583
I've been running with this on docs for a few days, with no problem. It
does not seem to address the threads running at 100% CPU at times though. But
assuming this fixes another problem, it
Github user atsci commented on the issue:
https://github.com/apache/trafficserver/pull/1620
clang format *successful*!
https://ci.trafficserver.apache.org/job/clang-format-github/121/
---
If your project is set up for it, you can reply to this email and have your
reply appear
Github user atsci commented on the issue:
https://github.com/apache/trafficserver/pull/1620
RAT check *successful*!
https://ci.trafficserver.apache.org/job/RAT-github/135/
---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub
Github user zwoop closed the pull request at:
https://github.com/apache/trafficserver/pull/1619
---
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
GitHub user zwoop opened a pull request:
https://github.com/apache/trafficserver/pull/1620
Adds a new condition, %{IP:}
This replaces the old %{CLIENT-IP}, and generalizes the access to
all four IP addresses. E.g.
cond %{SEND_RESPONSE_HDR_HOOK}
set-header
Github user atsci commented on the issue:
https://github.com/apache/trafficserver/pull/1619
clang-analyzer build *successful*!
https://ci.trafficserver.apache.org/job/clang-analyzer-github/378/
---
If your project is set up for it, you can reply to this email and have your
Github user atsci commented on the issue:
https://github.com/apache/trafficserver/pull/1619
Intel CC build *successful*!
https://ci.trafficserver.apache.org/job/icc-github/246/
---
If your project is set up for it, you can reply to this email and have your
reply appear on
Github user atsci commented on the issue:
https://github.com/apache/trafficserver/pull/1619
Linux build *successful*!
https://ci.trafficserver.apache.org/job/linux-github/1707/
---
If your project is set up for it, you can reply to this email and have your
reply appear on
Github user atsci commented on the issue:
https://github.com/apache/trafficserver/pull/1619
FreeBSD11 build *successful*!
https://ci.trafficserver.apache.org/job/freebsd-github/1816/
---
If your project is set up for it, you can reply to this email and have your
reply appear
Github user atsci commented on the issue:
https://github.com/apache/trafficserver/pull/1619
AU check *successful*!
https://ci.trafficserver.apache.org/job/autest-github/117/
---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub
Github user atsci commented on the issue:
https://github.com/apache/trafficserver/pull/1619
clang format *successful*!
https://ci.trafficserver.apache.org/job/clang-format-github/120/
---
If your project is set up for it, you can reply to this email and have your
reply appear
Github user atsci commented on the issue:
https://github.com/apache/trafficserver/pull/1619
RAT check *successful*!
https://ci.trafficserver.apache.org/job/RAT-github/134/
---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub
GitHub user vmamidi opened a pull request:
https://github.com/apache/trafficserver/pull/1619
Perform the config reload on ET_TASK threads
Config reload on a main thread could potentially block the requests on the
thread if the reload takes longer time.
You can merge this pull
Github user SolidWallOfCode commented on a diff in the pull request:
https://github.com/apache/trafficserver/pull/1608#discussion_r108767725
--- Diff: proxy/http/HttpConfig.cc ---
@@ -1129,6 +1129,8 @@ HttpConfig::startup()
// Local Manager
Github user bryancall commented on a diff in the pull request:
https://github.com/apache/trafficserver/pull/1557#discussion_r108756464
--- Diff: doc/admin-guide/plugins/gzip.en.rst ---
@@ -141,6 +141,26 @@ will leave the header intact if the client provided it.
- For when the
Github user bryancall commented on a diff in the pull request:
https://github.com/apache/trafficserver/pull/1557#discussion_r108756275
--- Diff: doc/admin-guide/plugins/gzip.en.rst ---
@@ -141,6 +141,26 @@ will leave the header intact if the client provided it.
- For when the
Github user bryancall commented on the issue:
https://github.com/apache/trafficserver/pull/1557
We should rip out enforce-brotli configuration option the same can be done
with multiple configs like the example below. We might want to add an allow
feature and use the ! syntax like
Github user SolidWallOfCode closed the pull request at:
https://github.com/apache/trafficserver/pull/1618
---
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
Github user atsci commented on the issue:
https://github.com/apache/trafficserver/pull/1618
clang-analyzer build *successful*!
https://ci.trafficserver.apache.org/job/clang-analyzer-github/377/
---
If your project is set up for it, you can reply to this email and have your
Github user atsci commented on the issue:
https://github.com/apache/trafficserver/pull/1618
Intel CC build *successful*!
https://ci.trafficserver.apache.org/job/icc-github/245/
---
If your project is set up for it, you can reply to this email and have your
reply appear on
Github user atsci commented on the issue:
https://github.com/apache/trafficserver/pull/1618
Linux build *successful*!
https://ci.trafficserver.apache.org/job/linux-github/1706/
---
If your project is set up for it, you can reply to this email and have your
reply appear on
Github user atsci commented on the issue:
https://github.com/apache/trafficserver/pull/1618
FreeBSD11 build *successful*!
https://ci.trafficserver.apache.org/job/freebsd-github/1815/
---
If your project is set up for it, you can reply to this email and have your
reply appear
Github user atsci commented on the issue:
https://github.com/apache/trafficserver/pull/1618
AU check *successful*!
https://ci.trafficserver.apache.org/job/autest-github/116/
---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub
Github user atsci commented on the issue:
https://github.com/apache/trafficserver/pull/1618
clang format *successful*!
https://ci.trafficserver.apache.org/job/clang-format-github/119/
---
If your project is set up for it, you can reply to this email and have your
reply appear
Github user atsci commented on the issue:
https://github.com/apache/trafficserver/pull/1618
RAT check *successful*!
https://ci.trafficserver.apache.org/job/RAT-github/133/
---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub
Github user SolidWallOfCode commented on the issue:
https://github.com/apache/trafficserver/pull/1618
Let's use member initialization.
---
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
Github user atsci commented on the issue:
https://github.com/apache/trafficserver/pull/1618
clang-analyzer build *successful*!
https://ci.trafficserver.apache.org/job/clang-analyzer-github/376/
---
If your project is set up for it, you can reply to this email and have your
Github user atsci commented on the issue:
https://github.com/apache/trafficserver/pull/1618
FreeBSD11 build *successful*!
https://ci.trafficserver.apache.org/job/freebsd-github/1814/
---
If your project is set up for it, you can reply to this email and have your
reply appear
Github user atsci commented on the issue:
https://github.com/apache/trafficserver/pull/1618
Linux build *successful*!
https://ci.trafficserver.apache.org/job/linux-github/1705/
---
If your project is set up for it, you can reply to this email and have your
reply appear on
Github user atsci commented on the issue:
https://github.com/apache/trafficserver/pull/1618
Intel CC build *successful*!
https://ci.trafficserver.apache.org/job/icc-github/244/
---
If your project is set up for it, you can reply to this email and have your
reply appear on
Github user atsci commented on the issue:
https://github.com/apache/trafficserver/pull/1618
AU check *successful*!
https://ci.trafficserver.apache.org/job/autest-github/115/
---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub
Github user atsci commented on the issue:
https://github.com/apache/trafficserver/pull/1618
clang format *successful*!
https://ci.trafficserver.apache.org/job/clang-format-github/118/
---
If your project is set up for it, you can reply to this email and have your
reply appear
Github user atsci commented on the issue:
https://github.com/apache/trafficserver/pull/1618
RAT check *successful*!
https://ci.trafficserver.apache.org/job/RAT-github/132/
---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub
GitHub user persiaAziz opened a pull request:
https://github.com/apache/trafficserver/pull/1618
Coverity1373100:Uninitialized member
You can merge this pull request into a Git repository by running:
$ git pull https://github.com/persiaAziz/trafficserver coverity
Github user atsci commented on the issue:
https://github.com/apache/trafficserver/pull/1617
clang-analyzer build *successful*!
https://ci.trafficserver.apache.org/job/clang-analyzer-github/375/
---
If your project is set up for it, you can reply to this email and have your
Github user atsci commented on the issue:
https://github.com/apache/trafficserver/pull/1617
Linux build *successful*!
https://ci.trafficserver.apache.org/job/linux-github/1704/
---
If your project is set up for it, you can reply to this email and have your
reply appear on
Github user atsci commented on the issue:
https://github.com/apache/trafficserver/pull/1617
Intel CC build *successful*!
https://ci.trafficserver.apache.org/job/icc-github/243/
---
If your project is set up for it, you can reply to this email and have your
reply appear on
Github user atsci commented on the issue:
https://github.com/apache/trafficserver/pull/1617
FreeBSD11 build *successful*!
https://ci.trafficserver.apache.org/job/freebsd-github/1813/
---
If your project is set up for it, you can reply to this email and have your
reply appear
Github user atsci commented on the issue:
https://github.com/apache/trafficserver/pull/1617
AU check *successful*!
https://ci.trafficserver.apache.org/job/autest-github/114/
---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub
Github user atsci commented on the issue:
https://github.com/apache/trafficserver/pull/1617
RAT check *successful*!
https://ci.trafficserver.apache.org/job/RAT-github/131/
---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub
Github user atsci commented on the issue:
https://github.com/apache/trafficserver/pull/1617
clang format *successful*!
https://ci.trafficserver.apache.org/job/clang-format-github/117/
---
If your project is set up for it, you can reply to this email and have your
reply appear
GitHub user oknet opened a pull request:
https://github.com/apache/trafficserver/pull/1617
The result of TSHttpTxnParentProxySet() maybe overwrite in
ParentConfigParams::findParent()
You can merge this pull request into a Git repository by running:
$ git pull
Github user clearswift commented on the issue:
https://github.com/apache/trafficserver/pull/1608
We decided that we need to dedicate some time to these issues and do not
anticipate having an update this week as we are busy on other matters.
---
If your project is set up for it, you
52 matches
Mail list logo