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 coding :-)CheersShmuel Krakower <firstname.lastname@example.org> schrieb am Mi., 22. Mai 2019, 22:29:Hi matt and lbutlrThanks 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" or stitch it with a proxy. I am using mod_proxy.My other alternative is to use other software than httpd to stitch those two services and show 200 instead of the 302.The solution mentioned in stackoverflow will not work for 302 response as I cannot set error page for such non-error response codes.The solution with rewrite won't work neither as I need to alter the response and not the request.On Wed, May 22, 2019, 10:37 PM Muggeridge, Matt <email@example.com> wrote:
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 responses are not valid, then hunt down and fix/remove the ‘redirect’ configuration options in either a .htaccess or some other configuration file.