Thanks Torsten,
I was reading and implementing a simple PerlResponseHandler script to set
the response status line/code.
It works fine as a standalone, but it seems like in conjuction with
mod_proxy, it has no affect.
It feels like this handler is not manipulating the response coming back
from
Hi,
you could use a mod_perl output filter handler to rewrite the response to
your needs based on the input.
Did that for some specific SaaS years ago and for some response with e.g. a
special header the filter answered somerhing totally different and
discarded the original response.
Happy
Hi matt and lbutlr
Thanks for the response.
I guess I should add few pieces of information.
The client is one SaaS and the backend is another SaaS. The backend returns
302 which is right but the client consider anything which is not 2xx as
error which cause it to retry.
Therefore I must "hack"
With a little googling, this technique looks promising…
https://stackoverflow.com/questions/15083481/how-can-i-replace-apache-http-code-404-to-200
* As I cannot alter the backend behaviour
Yet, you talk about using mod_substitute and mod_header to alter the server’s
behaviour. If the 302
