In our proprietary proxy we used the first approach. There were reserved name
spaces for core usage but only a single name for the error. Actually we had two
names one with an error number as value and a second one with a human readable
error text. A lot of state was made available this way and
I think they can see the updated headers but this doesn't help. A plugin can't
know if the next plugin in the chain needs the plain text or even if there is a
next plugin. So every plugin is doing the gzip at the end. The next plugin in
the chain then will ungzip again.
Regards,
Roland
-Or
Giving the plugins a defined order seems to be of general use. Given such a
capability you can then configure a ungzip plugin called first and a gzip
plugin called last.
Note however if no plugin in the middle modifies the body then neither ungzip
nor gzip is necessary and the body can stay com
It is quite possible that the SNI option is used to select an appropriate
certificate (usually web servers do this), when a plugin try to do this then
the existence of more than one callback to do this could be confusing. SNI is a
TLS option but there are others like ALPN so all of them could po
When chunked encoding is used then no content-length header should be present.
If you require / use the content length then this will fail.
Roland
-Original Message-
From: oksana fishman [mailto:oksana.fishman.1...@gmail.com]
Sent: Wednesday, February 13, 2013 5:13 PM
To: dev@trafficser
If the client is 1.1 compliant and sends the request with chunked encoding
then it should know that the server is 1.1.
Roland
-Original Message-
From: Alan M. Carroll [mailto:a...@network-geographics.com]
Sent: Monday, December 17, 2012 10:40 PM
To: Roland Zink
Subject: Re: chunked
Hi,
I try to develop a plugin for TS 3.2 to modify post data. This fails for
POST requests without content-length. There is a bug report TS-1335 (TS
crashed when null_transform running as a request transform) which reports
something similar.
In my case it seems to fail because of
HttpSM::st
