+1
I think the generic way is a good direction as well. Lua plugin
supports that initially because long ago i thought that will be used
more often.
On Wed, Oct 13, 2021 at 10:38 AM Sudheer Vinukonda
wrote:
>
> +1
> I like the generic API direction, and extending it to support other existing
>
+1
I like the generic API direction, and extending it to support other existing
controls in favor of a different API for each.
On Wednesday, October 13, 2021, 09:16:40 AM PDT, Leif Hedstrom
wrote:
Anyone have any thoughts on this? If not, lazy consensus will apply and I’ll
pick one (
+1
On Wednesday, October 13, 2021, 09:26:54 AM PDT, Alan M. Carroll
wrote:
This proposal is to add a configuration variable
(proxy.config.http.pristine_client_req) which enables making a copy of the user
agent request before any transaction hooks, and an API call to retrieve the
This proposal is to add a configuration variable
(proxy.config.http.pristine_client_req) which enables making a copy of the user
agent request before any transaction hooks, and an API call to retrieve the
pristine copy. In addition, it would rename TSHttpTxnPristineUrlGet as
TSHttpTxnPreRemapUr
> On Oct 13, 2021, at 9:08 AM, Alan M. Carroll wrote:
>
> Libswoc (https://github.com/solidwallofcode/libswoc), "Solid Wall Of C++"
> library, is a collection of C++ utility classes. They are based on existing
> ATS core classes, except for Lexicon. Documentation is available here -
> http:
Anyone have any thoughts on this? If not, lazy consensus will apply and I’ll
pick one (which would be to promote TSHttpTxnCntl() and deprecate the
overlapping APIs).
— Leif
> On Oct 5, 2021, at 7:40 AM, Leif Hedstrom wrote:
>
> Hi all,
>
> While poking around, looking for a way to turn off
Libswoc (https://github.com/solidwallofcode/libswoc), "Solid Wall Of C++"
library, is a collection of C++ utility classes. They are based on existing ATS
core classes, except for Lexicon. Documentation is available here -
http://docs.solidwallofcode.com/libswoc.
The correspondence is
sw
