Github user zwoop commented on the issue:
https://github.com/apache/trafficserver/pull/1197
Pretty sure I see other places where TCL hash is used, no? So this would
just make things worse, we'd get both TCL hash and STL hashes :-/.
---
If your project is set up for it, you can reply
Github user zwoop commented on the issue:
https://github.com/apache/trafficserver/pull/1197
Is this the only place where we use TCL hash now? If so, it seems we could
shoe horn something else here other than STL?
---
If your project is set up for it, you can reply to this email
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
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/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 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
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/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/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 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 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 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 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 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 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 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 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 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 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_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_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 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/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 commented on the issue:
https://github.com/apache/trafficserver/pull/1227
Hmmm, logging most metrics seems somewhat useless. What would be useful
would be to have generic access to the underlying data that is used to update
the metrics for that transactions
Github user zwoop closed the pull request at:
https://github.com/apache/trafficserver/pull/1234
---
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/1234
I think this will clear the clang analyzer errors too.
---
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/1235
Which Jira is this for ?
---
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/1234
TS-5063: Fixes coverity warnings and cleans up the temp string
The Vec seems overkill here, and makes things less nice when
managing the intermediary strings. The new code has issues
Github user zwoop commented on the issue:
https://github.com/apache/trafficserver/pull/1229
This needs to be updated with clang-format. Easiest is to just run
$ make clang-format
and then push the branch again to update the PR.
---
If your project is set up
Github user zwoop commented on a diff in the pull request:
https://github.com/apache/trafficserver/pull/1234#discussion_r89405035
--- Diff: mgmt/LocalManager.cc ---
@@ -950,29 +949,27 @@ LocalManager::startProxy(const char *onetime_options)
if (open_ports_p
Github user zwoop commented on the issue:
https://github.com/apache/trafficserver/pull/1225
Can we put this into tools/reports ? There's one other similar tool in
there.
---
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/1184
I'm still not convinced this is a particularly useful API, but it's also
fairly benign. However, I do feel that if we are going to do this, we should
make the prototype something like
Github user zwoop commented on the issue:
https://github.com/apache/trafficserver/pull/1218
Please add Milestones, Labels etc...
---
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 closed the pull request at:
https://github.com/apache/trafficserver/pull/1154
---
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/1166
TS-5024: Limits the gzip to 200 OK responses
You can merge this pull request into a Git repository by running:
$ git pull https://github.com/zwoop/trafficserver TS-5024
Alternatively
Github user zwoop commented on a diff in the pull request:
https://github.com/apache/trafficserver/pull/1167#discussion_r85967946
--- Diff: lib/cppapi/Request.cc ---
@@ -177,6 +177,23 @@ Request::getHeaders() const
return state_->headers_;
}
+void
+Requ
Github user zwoop commented on a diff in the pull request:
https://github.com/apache/trafficserver/pull/1166#discussion_r85968661
--- Diff: plugins/gzip/gzip.cc ---
@@ -480,8 +480,8 @@ gzip_transformable(TSHttpTxn txnp, bool server,
HostConfiguration *host_configur
Github user zwoop commented on the issue:
https://github.com/apache/trafficserver/pull/1171
EventSystem.o
../../../iocore/eventsystem/EventSystem.cc:38:7: error: unused variable
'iobuffer_advice' [-Werror,-Wunused-variable]
int iobuffer_advice = 0
Github user zwoop closed the pull request at:
https://github.com/apache/trafficserver/pull/1166
---
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/1164
Looks good to me. A future improvement would be that --enable-asan disables
the freelist. It's today pretty obnoxious to run with ASAN, since you have to
tell traffic_manager to pass along
Github user zwoop commented on a diff in the pull request:
https://github.com/apache/trafficserver/pull/1164#discussion_r85624763
--- Diff: configure.ac ---
@@ -188,6 +188,14 @@ AC_ARG_ENABLE([werror],
)
AC_MSG_RESULT([$enable_werror])
+# Enable ASAN
Github user zwoop commented on the issue:
https://github.com/apache/trafficserver/pull/958
Meh, lets not do 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 closed the pull request at:
https://github.com/apache/trafficserver/pull/958
---
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/1185
TS-5031: Use readdir() instead of readdir_r()
See http://lwn.net/Articles/696474/.
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/1185
---
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/1193
How does this leak? If the constructor of LogObject fails?
---
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 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 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 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 commented on the issue:
https://github.com/apache/trafficserver/pull/1154
@SolidWallOfCode I agree, file a lira :).
---
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/1152
[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/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 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 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 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 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 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 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 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 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 opened a pull request:
https://github.com/apache/trafficserver/pull/1238
TS-4429: Adds a --terse (-e) option for logstats, excludes % metrics
You can merge this pull request into a Git repository by running:
$ git pull https://github.com/zwoop/trafficserver
Github user zwoop commented on the issue:
https://github.com/apache/trafficserver/pull/1252
Hmmm, it seems we are incredibly inconsistent here. Why singling out this
one place for this change? Do we really need TS_INLINE in general? I notice we
turn off inlining via #define in some
GitHub user zwoop opened a pull request:
https://github.com/apache/trafficserver/pull/1255
TS-5087: Updates the AL2 license on all .po files
You can merge this pull request into a Git repository by running:
$ git pull https://github.com/zwoop/trafficserver TS-5087
GitHub user zwoop opened a pull request:
https://github.com/apache/trafficserver/pull/1256
TS-2109: Allows CC: no-cache objects to be stored in cache
However, we still honor the no-cache header, such that we perform an IMS
request against the origin to validate the request
Github user zwoop closed the pull request at:
https://github.com/apache/trafficserver/pull/1256
---
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/1259
Nice! Any details on what the impact / symptoms for this is?
---
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
Github user zwoop closed the pull request at:
https://github.com/apache/trafficserver/pull/1261
---
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/1265
TS-5087: Updates the AL2 license on all .po files
Cherry picks from master.
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/1255
---
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/1316
---
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 an issue:
https://github.com/apache/trafficserver/issues/1326
Core dump in SSLAccept / SSLNetVConnection::sslServerHandShakeEvent
We (@randall) ran into an odd crashes that seems fairly similar (but not
identical) to https://issues.apache.org/jira/browse/TS
Github user zwoop commented on the issue:
https://github.com/apache/trafficserver/pull/1325
Any takers on reviewing 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 closed the pull request at:
https://github.com/apache/trafficserver/pull/1325
---
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 issue at:
https://github.com/apache/trafficserver/issues/1323
---
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/1325#discussion_r96107247
--- Diff: lib/records/RecUtils.cc ---
@@ -419,7 +419,7 @@ RecDataSetFromString(RecDataT data_type, RecData
*data_dst, const char *data_str
Github user zwoop commented on the issue:
https://github.com/apache/trafficserver/issues/1323
I think this got broken with ced4da13279f834c381925f2ecd1649bfb459e8b.
---
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 the issue:
https://github.com/apache/trafficserver/pull/1324
Albeit reasonable, I don't think we should land this. There's a number of
places from ced4da13279f834c381925f2ecd1649bfb459e8b which changes "NULL" to
"nullptr" acciden
GitHub user zwoop opened a pull request:
https://github.com/apache/trafficserver/pull/1325
#1323 Restores the NULL string where appropriate
You can merge this pull request into a Git repository by running:
$ git pull https://github.com/zwoop/trafficserver #1323
Alternatively
Github user zwoop closed the pull request at:
https://github.com/apache/trafficserver/pull/1324
---
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/1319
Mr (!) The Oil Rig, ( :-) )
did you check with @bryancall if he's planning a 7.0.1 release? if not,
this is a moot point, 7.1.x will hopefully be released in 4 weeks.
---
If your
Github user zwoop commented on the issue:
https://github.com/apache/trafficserver/pull/1320
Marking this for 7.1.0, we really need this in.
---
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 opened an issue:
https://github.com/apache/trafficserver/issues/1322
Possibly crasher in HostDB serialization (disk sync)
Hi Thomas,
we're seeing this odd looking crash, fairly often:
```
#0 0x2d74337d in __libc_waitpid (pid
Github user zwoop commented on the issue:
https://github.com/apache/trafficserver/issues/1322
Pretty sure they had been running for a while (several days at least), but
let me check.
---
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/pull/1243
This might honestly be a back port candidate? Does this apply to 7.0.x as
well as 6.2.x ?
---
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/pull/1243
5.3.x is end-of-lifed, we're not doing any more releases of that.
---
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 the issue:
https://github.com/apache/trafficserver/pull/1236
[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/1239
I landed my changes, so now you have to resolve the conflicts. Sorry bro. :)
---
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/1238
---
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/1241
Seems two issues here:
1. clang-format
1. FreeBSD doesn't have a T_DNAME ?
---
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/issues/1237
I think think you can set a timeout
(proxy.config.http.transaction_active_timeout_in) which doesn't care if data is
being sent or not (it's a "hard" timeout on an active
Github user zwoop commented on the issue:
https://github.com/apache/trafficserver/pull/1240
How about this too:
```
diff --git a/ci/jenkins/bin/docs.sh b/ci/jenkins/bin/docs.sh
index 6754040..f5b2a17 100644
--- a/ci/jenkins/bin/docs.sh
+++ b/ci/jenkins/bin
Github user zwoop closed the pull request at:
https://github.com/apache/trafficserver/pull/1240
---
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/1227
@sekimura You want to take stab at adding this as Lua definitions? I
assume the intent would be to expose some of these constants in an internal Lua
table?
---
If your project is set up
601 - 700 of 896 matches
Mail list logo
