encoded POST data transform
Your interpretation seems reasonable, the catch is "the server is known to
be 1.1 compliant". Is it reasonable to infer that if the request is marked
as 1.1?
Friday, December 14, 2012, 6:51:20 AM, you wrote:
> The comment seem to indicate that a post request
Your interpretation seems reasonable, the catch is "the server is known to be
1.1 compliant". Is it reasonable to infer that if the request is marked as 1.1?
Friday, December 14, 2012, 6:51:20 AM, you wrote:
> The comment seem to indicate that a post request always needs a
> content-length heade
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