Manish,
TS doesn't natively buffer the entire origin response for someone to
possibly operate on it with something like TSHttpBodyGet(), it streams
it from origin to client (or cache to client as the case may be).
Using a transformation plugin, you get to intercept that streaming as
it occurs and
Hi Traffic Server Gurus,
Would appreciate some help here -- How can I access the underlying string or
char* for the body of the server response?
There are many functions for working with server response headers -
including URL, mime type, etc, but I see nothing for the body itself.
I am trying to
I have looked at the examples in the SDK doc, and couldn't see any example
of proxy operation that depends on the content of the body - Any suggestions
on how to obtain the string to inspect the body?
What I have tried does not seem to work ... and will appreciate any help.
Seems like I am missing
Hi Eric,
Thanks for the pointers.
>1. With a transformation plugin you could 'print' the full response -- but
where do you want to print it?
I'd like to print it as a debug message to stdio/stderr on the window in
which the program is running, and check on the transformations that are
applied to
Hi Manish,
1. With a transformation plugin you could 'print' the full response --
but where do you want to print it?
2. There is no HTML parsing inside TrafficServer. TS does not care
about content; it proxies/caches *anything* as long as it's served
over HTTP/HTTPS.
To solve your problem, you w
Hi folks,
I am developing a trafficserver plugin, and would like to find out
1. How can I print a origin server response sent to the trafficserver, e.g.,
the html document with embedded javascript etc.
2. Also, how can I detect specific strings in the response to do response
filtering? Is there an
