[GitHub] trafficserver issue #1595: TS-4976: Regularize plugins - lifecycle

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

[GitHub] trafficserver issue #1594: Early intervention APIs

Github user SolidWallOfCode commented on the issue: https://github.com/apache/trafficserver/pull/1594 The regression tests are dumping core, obviously that needs to be fixed. --- If your project is set up for it, you can reply to this email and have your reply appear on GitHub as

[GitHub] trafficserver issue #1595: TS-4976: Regularize plugins - lifecycle

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

[GitHub] trafficserver pull request #1594: Early intervention APIs

Github user SolidWallOfCode commented on a diff in the pull request: https://github.com/apache/trafficserver/pull/1594#discussion_r106767390 --- Diff: proxy/http/HttpProxyServerMain.cc --- @@ -214,7 +215,7 @@ MakeHttpProxyAcceptor(HttpProxyAcceptor , HttpProxyPort , unsigned

[GitHub] trafficserver issue #1595: TS-4976: Regularize plugins - lifecycle

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

[GitHub] trafficserver pull request #1594: Early intervention APIs

Github user SolidWallOfCode commented on a diff in the pull request: https://github.com/apache/trafficserver/pull/1594#discussion_r106767260 --- Diff: proxy/InkAPI.cc --- @@ -9112,6 +9113,66 @@ TSSslContextDestroy(TSSslContext ctx) SSLReleaseContext(reinterpret_cast(ctx));

[GitHub] trafficserver issue #1595: TS-4976: Regularize plugins - lifecycle

Github user atsci commented on the issue: https://github.com/apache/trafficserver/pull/1595 Intel CC build *successful*! https://ci.trafficserver.apache.org/job/icc-github/210/ --- If your project is set up for it, you can reply to this email and have your reply appear on

[GitHub] trafficserver issue #1595: TS-4976: Regularize plugins - lifecycle

Github user atsci commented on the issue: https://github.com/apache/trafficserver/pull/1595 AU check *successful*! https://ci.trafficserver.apache.org/job/autest-github/81/ --- If your project is set up for it, you can reply to this email and have your reply appear on GitHub

[GitHub] trafficserver pull request #1594: Early intervention APIs

Github user SolidWallOfCode commented on a diff in the pull request: https://github.com/apache/trafficserver/pull/1594#discussion_r106767060 --- Diff: iocore/net/P_SSLNetVConnection.h --- @@ -259,6 +260,12 @@ class SSLNetVConnection : public UnixNetVConnection /// Set by

[GitHub] trafficserver issue #1595: TS-4976: Regularize plugins - lifecycle

Github user atsci commented on the issue: https://github.com/apache/trafficserver/pull/1595 RAT check *successful*! https://ci.trafficserver.apache.org/job/RAT-github/97/ --- If your project is set up for it, you can reply to this email and have your reply appear on GitHub as

[GitHub] trafficserver issue #1595: TS-4976: Regularize plugins - lifecycle

Github user atsci commented on the issue: https://github.com/apache/trafficserver/pull/1595 clang format *successful*! https://ci.trafficserver.apache.org/job/clang-format-github/84/ --- If your project is set up for it, you can reply to this email and have your reply appear

[GitHub] trafficserver pull request #1594: Early intervention APIs

Github user SolidWallOfCode commented on a diff in the pull request: https://github.com/apache/trafficserver/pull/1594#discussion_r106766812 --- Diff: iocore/net/P_SSLNetVConnection.h --- @@ -295,7 +302,7 @@ class SSLNetVConnection : public UnixNetVConnection

[GitHub] trafficserver pull request #1595: TS-4976: Regularize plugins - lifecycle

GitHub user SolidWallOfCode opened a pull request: https://github.com/apache/trafficserver/pull/1595 TS-4976: Regularize plugins - lifecycle Incremental work on #1114. You can merge this pull request into a Git repository by running: $ git pull

[GitHub] trafficserver issue #1557: brotli support in gzip plugin

Github user myraid commented on the issue: https://github.com/apache/trafficserver/pull/1557 @shukitchan @bryancall can you guys 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

Jenkins build is back to normal : ubuntu_14_04-master » gcc,ubuntu_14_04,release #2506

See

Build failed in Jenkins: ubuntu_14_04-master » gcc,ubuntu_14_04,release #2505

See -- [...truncated 2.87 MB...] *** TEST 62 *** STARTING *** *** TEST 62 *** PASSED *** *** TEST 63 *** STARTING *** *** TEST

[GitHub] trafficserver issue #1594: Early intervention APIs

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

[GitHub] trafficserver pull request #1592: TS-4976: Regularize plugins - hello

Github user SolidWallOfCode closed the pull request at: https://github.com/apache/trafficserver/pull/1592 --- 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] trafficserver issue #1592: TS-4976: Regularize plugins - hello

Github user SolidWallOfCode commented on the issue: https://github.com/apache/trafficserver/pull/1592 All the changes are related to the hello plugin or its use in the documentation. I will try to be more verbose in the future, however. --- If your project is set up for it, you can

[GitHub] trafficserver issue #1594: Early intervention APIs

Github user atsci commented on the issue: https://github.com/apache/trafficserver/pull/1594 Intel CC build *failed*! https://ci.trafficserver.apache.org/job/icc-github/209/ --- If your project is set up for it, you can reply to this email and have your reply appear on GitHub

[GitHub] trafficserver issue #1594: Early intervention APIs

Github user atsci commented on the issue: https://github.com/apache/trafficserver/pull/1594 AU check *successful*! https://ci.trafficserver.apache.org/job/autest-github/80/ --- If your project is set up for it, you can reply to this email and have your reply appear on GitHub

[GitHub] trafficserver issue #1594: Early intervention APIs

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

[GitHub] trafficserver issue #1594: Early intervention APIs

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

[GitHub] trafficserver issue #1594: Early intervention APIs

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

[GitHub] trafficserver issue #1594: Early intervention APIs

Github user atsci commented on the issue: https://github.com/apache/trafficserver/pull/1594 RAT check *successful*! https://ci.trafficserver.apache.org/job/RAT-github/96/ --- If your project is set up for it, you can reply to this email and have your reply appear on GitHub as

[GitHub] trafficserver issue #1594: Early intervention APIs

Github user atsci commented on the issue: https://github.com/apache/trafficserver/pull/1594 clang format *failed*! https://ci.trafficserver.apache.org/job/clang-format-github/83/ --- If your project is set up for it, you can reply to this email and have your reply appear on

[GitHub] trafficserver issue #1557: brotli support in gzip plugin

Github user myraid commented on the issue: https://github.com/apache/trafficserver/pull/1557 Yes we could enforce brotli encoding by overriding the Accept-Encoding to "br" if we are OK with origin responding with plain text. Infact this is cleaner approach. Do we have to worry

[GitHub] trafficserver issue #1594: Early intervention APIs

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

[GitHub] trafficserver issue #1594: Early intervention APIs

Github user atsci commented on the issue: https://github.com/apache/trafficserver/pull/1594 Intel CC build *failed*! https://ci.trafficserver.apache.org/job/icc-github/208/ --- If your project is set up for it, you can reply to this email and have your reply appear on GitHub

[GitHub] trafficserver issue #1594: Early intervention APIs

Github user atsci commented on the issue: https://github.com/apache/trafficserver/pull/1594 clang format *successful*! https://ci.trafficserver.apache.org/job/clang-format-github/82/ --- If your project is set up for it, you can reply to this email and have your reply appear

[GitHub] trafficserver issue #1594: Early intervention APIs

Github user atsci commented on the issue: https://github.com/apache/trafficserver/pull/1594 RAT check *successful*! https://ci.trafficserver.apache.org/job/RAT-github/95/ --- If your project is set up for it, you can reply to this email and have your reply appear on GitHub as

[GitHub] trafficserver issue #1594: Early intervention APIs

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

[GitHub] trafficserver issue #1594: Early intervention APIs

Github user atsci commented on the issue: https://github.com/apache/trafficserver/pull/1594 AU check *failed*! https://ci.trafficserver.apache.org/job/autest-github/79/ --- If your project is set up for it, you can reply to this email and have your reply appear on GitHub as

[GitHub] trafficserver pull request #1594: Early intervention APIs

GitHub user persiaAziz opened a pull request: https://github.com/apache/trafficserver/pull/1594 Early intervention APIs This PR contains: -> APIs for early intervention -> docs -> example plugin to show the usage You can merge this pull request into a Git repository by

[GitHub] trafficserver issue #1557: brotli support in gzip plugin

Github user shukitchan commented on the issue: https://github.com/apache/trafficserver/pull/1557 wouldn't it be easier if "enforce-brotli" will override the "Accept-Encoding" to "br"? So the origin will either return plain text or brotli encoded data. And the plugin only need to

[GitHub] trafficserver issue #1593: Thread "hangs" on Docs

GitHub user zwoop opened an issue: https://github.com/apache/trafficserver/issues/1593 Thread "hangs" on Docs Running latest 7.1.x branch on Docs with #1583 as well, I started seeing a thread consuming a *lot* of CPU. In the order of 1000x more than the other threads (3-5 CPU

[GitHub] trafficserver issue #1592: TS-4976: Regularize plugins - hello

Github user zwoop commented on the issue: https://github.com/apache/trafficserver/pull/1592 Why did the AU check fail? Did you forget to rebase? :) --- 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

[GitHub] trafficserver issue #1497: Doc: change .svg to .png.

Github user zwoop commented on the issue: https://github.com/apache/trafficserver/pull/1497 Yeh, that's fine, I upgraded Sphinx long ago on the Docs build box. --- 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] trafficserver issue #1557: brotli support in gzip plugin

Github user myraid commented on the issue: https://github.com/apache/trafficserver/pull/1557 @shukitchan My Comments inline 1. I think we need to maintain the existing behavior as much as possible. So perhaps the default for the new configuration option

[GitHub] trafficserver issue #1497: Doc: change .svg to .png.

Github user SolidWallOfCode commented on the issue: https://github.com/apache/trafficserver/pull/1497 I think I will update to require Sphinx 1.5.1 instead. That's in general availability. --- If your project is set up for it, you can reply to this email and have your reply appear

[GitHub] trafficserver pull request #1547: Fix ssl hook state logic.

Github user SolidWallOfCode closed the pull request at: https://github.com/apache/trafficserver/pull/1547 --- 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] trafficserver pull request #1502: issue #1501: reconstruct to load the defau...

Github user SolidWallOfCode closed the pull request at: https://github.com/apache/trafficserver/pull/1502 --- 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] trafficserver issue #1592: TS-4976: Regularize plugins - hello

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

[GitHub] trafficserver issue #1592: TS-4976: Regularize plugins - hello

Github user atsci commented on the issue: https://github.com/apache/trafficserver/pull/1592 Intel CC build *successful*! https://ci.trafficserver.apache.org/job/icc-github/207/ --- If your project is set up for it, you can reply to this email and have your reply appear on

[GitHub] trafficserver issue #1592: TS-4976: Regularize plugins - hello

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

[GitHub] trafficserver issue #1592: TS-4976: Regularize plugins - hello

Github user atsci commented on the issue: https://github.com/apache/trafficserver/pull/1592 AU check *failed*! https://ci.trafficserver.apache.org/job/autest-github/78/ --- If your project is set up for it, you can reply to this email and have your reply appear on GitHub as

[GitHub] trafficserver issue #1592: TS-4976: Regularize plugins - hello

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

[GitHub] trafficserver issue #1592: TS-4976: Regularize plugins - hello

Github user atsci commented on the issue: https://github.com/apache/trafficserver/pull/1592 RAT check *successful*! https://ci.trafficserver.apache.org/job/RAT-github/94/ --- If your project is set up for it, you can reply to this email and have your reply appear on GitHub as

[GitHub] trafficserver issue #1592: TS-4976: Regularize plugins - hello

Github user atsci commented on the issue: https://github.com/apache/trafficserver/pull/1592 clang format *successful*! https://ci.trafficserver.apache.org/job/clang-format-github/81/ --- If your project is set up for it, you can reply to this email and have your reply appear

[GitHub] trafficserver pull request #1592: TS-4976: Regularize plugins - hello

GitHub user SolidWallOfCode opened a pull request: https://github.com/apache/trafficserver/pull/1592 TS-4976: Regularize plugins - hello Incremental work on #1114. You can merge this pull request into a Git repository by running: $ git pull

[GitHub] trafficserver pull request #1581: TS-4976: Regularize plugins - file

Github user SolidWallOfCode closed the pull request at: https://github.com/apache/trafficserver/pull/1581 --- 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] trafficserver issue #1516: Implement Cache-Control: immutable handling

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

[GitHub] trafficserver issue #1516: Implement Cache-Control: immutable handling

Github user atsci commented on the issue: https://github.com/apache/trafficserver/pull/1516 Intel CC build *successful*! https://ci.trafficserver.apache.org/job/icc-github/206/ --- If your project is set up for it, you can reply to this email and have your reply appear on

[GitHub] trafficserver issue #1516: Implement Cache-Control: immutable handling

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

[GitHub] trafficserver issue #1516: Implement Cache-Control: immutable handling

Github user atsci commented on the issue: https://github.com/apache/trafficserver/pull/1516 RAT check *successful*! https://ci.trafficserver.apache.org/job/RAT-github/93/ --- If your project is set up for it, you can reply to this email and have your reply appear on GitHub as

[GitHub] trafficserver issue #1516: Implement Cache-Control: immutable handling

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

[GitHub] trafficserver issue #1516: Implement Cache-Control: immutable handling

Github user atsci commented on the issue: https://github.com/apache/trafficserver/pull/1516 AU check *successful*! https://ci.trafficserver.apache.org/job/autest-github/77/ --- If your project is set up for it, you can reply to this email and have your reply appear on GitHub

[GitHub] trafficserver issue #1516: Implement Cache-Control: immutable handling

Github user atsci commented on the issue: https://github.com/apache/trafficserver/pull/1516 clang format *successful*! https://ci.trafficserver.apache.org/job/clang-format-github/80/ --- If your project is set up for it, you can reply to this email and have your reply appear

[GitHub] trafficserver issue #1516: Implement Cache-Control: immutable handling

Github user danobi commented on the issue: https://github.com/apache/trafficserver/pull/1516 done --- 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] trafficserver issue #1557: brotli support in gzip plugin

Github user shukitchan commented on the issue: https://github.com/apache/trafficserver/pull/1557 two more points 1) I think we need to maintain the existing behavior as much as possible. So perhaps the default for the new configuration option "supported-algorithms" should

[GitHub] trafficserver issue #1516: Implement Cache-Control: immutable handling

Github user shukitchan commented on the issue: https://github.com/apache/trafficserver/pull/1516 can you squash now? then i can verify and merge. --- 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

[GitHub] trafficserver issue #1591: Advertised header table size is not used

GitHub user maskit opened an issue: https://github.com/apache/trafficserver/issues/1591 Advertised header table size is not used Current implementation doesn't use the advertised header table size. To reproduce: ``` $ nghttp -nv -c 1024 https://localhost/ ```