Github user zwoop closed the pull request at:
https://github.com/apache/trafficserver/pull/1150
---
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 closed the pull request at:
https://github.com/apache/trafficserver/pull/1151
---
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/1154
TS-5011: Fixes memory leak in CLFUS compression
You can merge this pull request into a Git repository by running:
$ git pull https://github.com/zwoop/trafficserver TS-5011
Github user zwoop commented on the issue:
https://github.com/apache/trafficserver/pull/1154
[approve ci]
---
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
GitHub user zwoop opened a pull request:
https://github.com/apache/trafficserver/pull/1151
TS-5010: Initialize the regex pointer properly
You can merge this pull request into a Git repository by running:
$ git pull https://github.com/zwoop/trafficserver TS-5010
Alternatively
Github user zwoop commented on the issue:
https://github.com/apache/trafficserver/pull/1149
[approve ci]
---
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
Github user zwoop closed the pull request at:
https://github.com/apache/trafficserver/pull/1146
---
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 commented on the issue:
https://github.com/apache/trafficserver/pull/1148
Does this need to go into 7.0.0 as well? @bryancall
---
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
Github user zwoop commented on a diff in the pull request:
https://github.com/apache/trafficserver/pull/1140#discussion_r85228363
--- Diff: proxy/http/HttpSM.cc ---
@@ -3309,7 +3309,7 @@ HttpSM::tunnel_handler_ua(int event,
HttpTunnelConsumer *c)
// only external
Github user zwoop commented on the issue:
https://github.com/apache/trafficserver/pull/1140
This needs a Jira number.
---
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
GitHub user zwoop opened a pull request:
https://github.com/apache/trafficserver/pull/1146
TS-5005: CID 1364117: Explicit null dereferenced in HttpSM.cc
Probably benign, since the vc shouldn't be NULL, but coverity is ruling
with an iron fist.
You can merge this pull request
Github user zwoop closed the pull request at:
https://github.com/apache/trafficserver/pull/1143
---
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 commented on the issue:
https://github.com/apache/trafficserver/pull/1142
You should use the Jira number.
---
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 zwoop opened a pull request:
https://github.com/apache/trafficserver/pull/1143
TS-4582: Do not allow multiple --policy arguments
You can merge this pull request into a Git repository by running:
$ git pull https://github.com/zwoop/trafficserver TS-4582
Github user zwoop closed the pull request at:
https://github.com/apache/trafficserver/pull/1137
---
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/1136
TS-5000: Moves experimental plugins to the new include mechanism
You can merge this pull request into a Git repository by running:
$ git pull https://github.com/zwoop/trafficserver TS
Github user zwoop commented on the issue:
https://github.com/apache/trafficserver/pull/1133
Randall and I ran into another issue with this patch, so doing some more
debugging :-/.
---
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 a diff in the pull request:
https://github.com/apache/trafficserver/pull/1133#discussion_r84770706
--- Diff: plugins/header_rewrite/parser.cc ---
@@ -133,14 +152,15 @@ Parser::preprocess(std::vector tokens)
std::string s = tokens[0].substr
Github user zwoop commented on a diff in the pull request:
https://github.com/apache/trafficserver/pull/1133#discussion_r84729282
--- Diff: plugins/header_rewrite/header_rewrite_test.cc ---
@@ -31,274 +33,395 @@ const char PLUGIN_NAME_DBG[] =
"TEST_dbg_header_rewrite";
Github user zwoop commented on a diff in the pull request:
https://github.com/apache/trafficserver/pull/1133#discussion_r84723539
--- Diff: plugins/header_rewrite/header_rewrite_test.cc ---
@@ -31,274 +33,395 @@ const char PLUGIN_NAME_DBG[] =
"TEST_dbg_header_rewrite";
Github user zwoop commented on a diff in the pull request:
https://github.com/apache/trafficserver/pull/1133#discussion_r84770538
--- Diff: plugins/header_rewrite/parser.cc ---
@@ -133,14 +152,15 @@ Parser::preprocess(std::vector tokens)
std::string s = tokens[0].substr
Github user zwoop commented on a diff in the pull request:
https://github.com/apache/trafficserver/pull/1133#discussion_r84770458
--- Diff: plugins/header_rewrite/header_rewrite_test.cc ---
@@ -31,274 +33,395 @@ const char PLUGIN_NAME_DBG[] =
"TEST_dbg_header_rewrite";
Github user zwoop commented on the issue:
https://github.com/apache/trafficserver/pull/1134
Hmmm, are we sure this makes sense? The CPP APIs aren't plugins, and we
certainly don't put the TS API's into plugins. I could perhaps see this go into
proxy somewhere.
---
If your project
GitHub user zwoop opened a pull request:
https://github.com/apache/trafficserver/pull/1133
TS-4993: Disables escaping and quotes inside regexes
In addition, this cleans up the unit tests a bit, to make it more useful
from
the command line when testing/debugging. New tests
Github user zwoop commented on the issue:
https://github.com/apache/trafficserver/pull/1128
@jsime Can you review please?
---
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
GitHub user zwoop opened a pull request:
https://github.com/apache/trafficserver/pull/1129
TS-4992: Do not build the static libraries
You can merge this pull request into a Git repository by running:
$ git pull https://github.com/zwoop/trafficserver TS-4992
Alternatively you
Github user zwoop commented on the issue:
https://github.com/apache/trafficserver/pull/1125
I see. The first portion of this patch is important, whereas the second
portion is done (better?) in #1079.
---
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/1115
Besides the failures ( ;-) ) I think this is something we should do. It's a
fairly simple change (hopefully), retains the modularity (by retaining the
Makefile.inc's and then include them
Github user zwoop commented on the issue:
https://github.com/apache/trafficserver/pull/1125
Looking back, it seems this is basically handled (but better) with #1079 ?
---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well
Github user zwoop closed the pull request at:
https://github.com/apache/trafficserver/pull/1117
---
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 commented on the issue:
https://github.com/apache/trafficserver/pull/1117
Sigh, it failed again on the bison generated files :-/. [approve ci].
---
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 zwoop commented on a diff in the pull request:
https://github.com/apache/trafficserver/pull/1117#discussion_r83908521
--- Diff: proxy/http2/Http2Stream.cc ---
@@ -675,6 +675,17 @@ Http2Stream::destroy()
}
chunked_handler.clear();
super::destroy
Github user zwoop commented on a diff in the pull request:
https://github.com/apache/trafficserver/pull/1116#discussion_r83893797
--- Diff: proxy/http/HttpTransact.cc ---
@@ -1075,6 +1073,8 @@ HttpTransact::ModifyRequest(State *s)
if (!request.is_target_in_url
Github user zwoop closed the pull request at:
https://github.com/apache/trafficserver/pull/1078
---
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 commented on the issue:
https://github.com/apache/trafficserver/pull/1109
Is this a duplicate PR?
---
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
Github user zwoop commented on the issue:
https://github.com/apache/trafficserver/pull/1114
Clang format
---
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
Github user zwoop closed the pull request at:
https://github.com/apache/trafficserver/pull/1090
---
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 closed the pull request at:
https://github.com/apache/trafficserver/pull/1101
---
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 commented on the issue:
https://github.com/apache/trafficserver/pull/1101
Rebuilding again, because I think the trees on the buildbots was busted
[approve ci].
---
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/1100
Try again [approve ci].
---
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
Github user zwoop commented on the issue:
https://github.com/apache/trafficserver/pull/1100
Try again [approve ci].
---
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
GitHub user zwoop opened a pull request:
https://github.com/apache/trafficserver/pull/1101
TS-4959: Remove remnants of old UA configurations and handling
I made this as two commits:
1) Remove some definitely strange code around MSIE.
2) Remove all the code around
Github user zwoop commented on the issue:
https://github.com/apache/trafficserver/pull/1100
Just a heads up, but this PR is against 6.2.x branch, the code has
diverged, so will need one PR for 6.2.x and one for master. @gtenev Please make
a PR for master at your earliest convenience
Github user zwoop commented on the issue:
https://github.com/apache/trafficserver/pull/1099
@gtenev This looks very strange, did you pull/rebase your tree first?
---
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 zwoop closed the pull request at:
https://github.com/apache/trafficserver/pull/1081
---
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 commented on a diff in the pull request:
https://github.com/apache/trafficserver/pull/1097#discussion_r82917530
--- Diff: mgmt/RecordsConfig.cc ---
@@ -1449,6 +1449,8 @@ static const RecordElement RecordsConfig[] =
,
{RECT_CONFIG
Github user zwoop commented on the issue:
https://github.com/apache/trafficserver/pull/1088
Clang-format ...
---
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
Github user zwoop commented on the issue:
https://github.com/apache/trafficserver/pull/1090
I'll leave this sitting for another day or so, we had already (in April I
think) marked these as deprecated for 6.2.0, and no one objected then either.
---
If your project is set up
Github user zwoop commented on the issue:
https://github.com/apache/trafficserver/pull/1089
Maybe you have to rebase this from master, to get the clang-format fixes
that were done yesterday.
---
If your project is set up for it, you can reply to this email and have your
reply appear
GitHub user zwoop opened a pull request:
https://github.com/apache/trafficserver/pull/1090
TS-4949: Disables the fuzzy revalidation logic by default
You can merge this pull request into a Git repository by running:
$ git pull https://github.com/zwoop/trafficserver TS-4949
GitHub user zwoop opened a pull request:
https://github.com/apache/trafficserver/pull/1087
TS-4945: Remove unused member variable, epoll_vc
CID 1364096
You can merge this pull request into a Git repository by running:
$ git pull https://github.com/zwoop/trafficserver TS-4945
Github user zwoop closed the pull request at:
https://github.com/apache/trafficserver/pull/1076
---
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 commented on the issue:
https://github.com/apache/trafficserver/pull/1076
Yes, they would have TTLs, but if I turned off syncing, I certainly
wouldn't expect it to load something old. What if I had bad entries? What if I
had a corruption of some sort? Since
Github user zwoop commented on the issue:
https://github.com/apache/trafficserver/pull/1078
Try build on freebsd again [approve ci].
---
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
Github user zwoop commented on the issue:
https://github.com/apache/trafficserver/pull/1074
I'd imagine this is a backport candidate for at least 7.0.0, maybe 6.2.x ?
---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well
Github user zwoop commented on the issue:
https://github.com/apache/trafficserver/pull/1074
@gtenev Can you review this please?
---
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 zwoop opened a pull request:
https://github.com/apache/trafficserver/pull/1078
TS-4930: Unfolds request headers that are using obs continuations
I also removed a file that is basically a duplication of another file, and
this duplicated file is not used at all
GitHub user zwoop opened a pull request:
https://github.com/apache/trafficserver/pull/1076
TS-4929: No loading of HostDB disk file if sync_frequency=0
This has two benefit (2) is most important I think:
1) We avoid warnings on startup about not being able to load the HostDB
Github user zwoop commented on the issue:
https://github.com/apache/trafficserver/issues/1071
Right, but your comments say "replaces". I think we should keep both,
indefinitely.
---
If your project is set up for it, you can reply to this email and have your
reply appear
Github user zwoop commented on the issue:
https://github.com/apache/trafficserver/issues/1071
We should make the old behavior optional to enable as well, there's a
significant number of backends (origins) that do not support RFC7239 yet but
need the old semantics.
---
If your
Github user zwoop commented on the issue:
https://github.com/apache/trafficserver/pull/1067
Mostly out of curiosity, is there a particular header here in the (limited)
set of headers that is likely to have multi-values?
---
If your project is set up for it, you can reply
Github user zwoop commented on the issue:
https://github.com/apache/trafficserver/pull/1066
I'm generally ok with this, up to you if you wish to clean anything up.
---
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 zwoop commented on a diff in the pull request:
https://github.com/apache/trafficserver/pull/1066#discussion_r81416662
--- Diff: proxy/http/HttpTransactHeaders.cc ---
@@ -812,26 +813,16 @@
HttpTransactHeaders::insert_via_header_in_response(HttpTransact::State *s, HTTPH
Github user zwoop commented on a diff in the pull request:
https://github.com/apache/trafficserver/pull/1066#discussion_r81413339
--- Diff: proxy/http/HttpTransactHeaders.cc ---
@@ -812,26 +813,16 @@
HttpTransactHeaders::insert_via_header_in_response(HttpTransact::State *s, HTTPH
Github user zwoop commented on a diff in the pull request:
https://github.com/apache/trafficserver/pull/1066#discussion_r81411258
--- Diff: proxy/http/HttpTransactHeaders.cc ---
@@ -812,26 +813,16 @@
HttpTransactHeaders::insert_via_header_in_response(HttpTransact::State *s, HTTPH
Github user zwoop commented on a diff in the pull request:
https://github.com/apache/trafficserver/pull/1066#discussion_r81415497
--- Diff: proxy/http/HttpTransactHeaders.cc ---
@@ -812,26 +813,16 @@
HttpTransactHeaders::insert_via_header_in_response(HttpTransact::State *s, HTTPH
Github user zwoop commented on the issue:
https://github.com/apache/trafficserver/pull/502
Ping on this? Do we still want to move along with this?
---
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
Github user zwoop commented on the issue:
https://github.com/apache/trafficserver/pull/1055
[approve ci]
---
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
Github user zwoop commented on the issue:
https://github.com/apache/trafficserver/pull/1025
Should we land this?
---
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
Github user zwoop commented on the issue:
https://github.com/apache/trafficserver/pull/1052
I tried this on docs, and it fails fast:
```
(gdb) bt
#0 0x740305f7 in __GI_raise (sig=sig@entry=6) at
../nptl/sysdeps/unix/sysv/linux/raise.c:56
#1
Github user zwoop closed the pull request at:
https://github.com/apache/trafficserver/pull/1035
---
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 commented on the issue:
https://github.com/apache/trafficserver/pull/963
@ngara Maybe I'm reading this wrong, but it looks like we still have 3
commits in this PR. If that's the case, can you please squash that down into a
single commit? No reason to have the 2
Github user zwoop commented on the issue:
https://github.com/apache/trafficserver/pull/1028
@jpeach we ok to land this now?
---
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 zwoop opened a pull request:
https://github.com/apache/trafficserver/pull/1035
TS-4866: Makes traffic_cop killing optional
This adds a new configuration option, proxy.config.cop.active_health_checks:
0 - traffic_cop is not allowed to kill any processes
1
Github user zwoop closed the pull request at:
https://github.com/apache/trafficserver/pull/749
---
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 commented on the issue:
https://github.com/apache/trafficserver/pull/1024
[approve ci]
---
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
Github user zwoop closed the pull request at:
https://github.com/apache/trafficserver/pull/993
---
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 commented on the issue:
https://github.com/apache/trafficserver/pull/993
Alan, no, it'll work afaik. It'll only fail if you go out of the way and
remove the IPv6 kernel module.
---
If your project is set up for it, you can reply to this email and have your
reply
Github user zwoop commented on the issue:
https://github.com/apache/trafficserver/pull/1014
Please test on docs, cursory code review looks good.
:+1:
---
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 zwoop closed the pull request at:
https://github.com/apache/trafficserver/pull/995
---
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 commented on the issue:
https://github.com/apache/trafficserver/pull/1010
Clang-forma, trailing white spaces here:
```C++
-} else {
+} else {
```
---
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/1010
[approve ci]
---
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
Github user zwoop commented on the issue:
https://github.com/apache/trafficserver/pull/1009
[approve ci]
---
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
Github user zwoop commented on the issue:
https://github.com/apache/trafficserver/pull/1007
[approve ci]
---
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
Github user zwoop commented on the issue:
https://github.com/apache/trafficserver/pull/1006
Clang format i think
---
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
Github user zwoop commented on the issue:
https://github.com/apache/trafficserver/pull/834
IMO, the proposal of fname and maxdirs is a bit of a hack, solving a subset
of all possible use cases. Allowing for a "parent selection URL" that can be
the same, or diffe
Github user zwoop commented on a diff in the pull request:
https://github.com/apache/trafficserver/pull/834#discussion_r78286562
--- Diff: proxy/api/ts/ts.h ---
@@ -1481,6 +1481,9 @@ tsapi TSReturnCode TSHttpTxnParentProxyGet(TSHttpTxn
txnp, const char **hostname
GitHub user zwoop opened a pull request:
https://github.com/apache/trafficserver/pull/1004
TS-4641 Changes default for proxy.config.cache.hostdb.sync_frequency â¦
â¦to 0
You can merge this pull request into a Git repository by running:
$ git pull https://github.com/zwoop
Github user zwoop closed the pull request at:
https://github.com/apache/trafficserver/pull/1003
---
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 commented on the issue:
https://github.com/apache/trafficserver/pull/1003
It's a bummer, but seems devtoolset-3 on CentOS6 does not agree with
-std=c11.
---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well
GitHub user zwoop opened a pull request:
https://github.com/apache/trafficserver/pull/1003
TS-4752 Changes CFLAGS from -std=gnu99 to -std=c11
You can merge this pull request into a Git repository by running:
$ git pull https://github.com/zwoop/trafficserver TS-4752
Github user zwoop commented on the issue:
https://github.com/apache/trafficserver/pull/977
:+1:
---
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
GitHub user zwoop opened a pull request:
https://github.com/apache/trafficserver/pull/995
TS-4731: Changes return codes for IsInternal APIs
This changes the following APIs:
tsapi int TSHttpTxnIsInternal(TSHttpTxn txnp);
tsapi int TSHttpSsnIsInternal(TSHttpSsn ssnp
Github user zwoop commented on the issue:
https://github.com/apache/trafficserver/pull/995
Whomever is reviewing: Please make sure I got all the conditionals right,
with the correct boolean logic.
---
If your project is set up for it, you can reply to this email and have your
reply
Github user zwoop commented on the issue:
https://github.com/apache/trafficserver/pull/991
```
../../proxy/http/remap/UrlMapping.h:30:19: fatal error: Error.h: No such
file or directory
#include "Error.h"
```
---
If your project is set up for it, you
GitHub user zwoop opened a pull request:
https://github.com/apache/trafficserver/pull/993
TS-4068: Changes default for server_ports to include IPv6
You can merge this pull request into a Git repository by running:
$ git pull https://github.com/zwoop/trafficserver TS-4068
Github user zwoop commented on the issue:
https://github.com/apache/trafficserver/pull/984
Looks 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 have this feature
enabled
Github user zwoop commented on the issue:
https://github.com/apache/trafficserver/pull/701
Status on this?
---
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
Github user zwoop commented on the issue:
https://github.com/apache/trafficserver/pull/989
:+1:
---
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
Github user zwoop commented on the issue:
https://github.com/apache/trafficserver/pull/977
Looks good, but fails on FreeBSD for some reason:
{code}
../../../iocore/net/SSLUtils.cc:384:27: error: use of undeclared identifier
'TS_SSL_CERT_EVENT'; did you mean
501 - 600 of 896 matches
Mail list logo
