Apache not passing through 404 error from API behind reverse proxy

Question

When I make a call using Postman to my API - which is behind a reverse proxy using Apache 2.2 - that returns a 404, I get the standard 404 Not Found html returned instead of the error from the API.

How can I configure Apache to return the error from the API instead of serving it's own HTML?

The route lives inside a <Location> block:

<Location /service/api>
    ProxyPass http://docker1:6001
    ProxyPassReverse http://docker1:6001
</Location>

An example 404 call would be http://example.com/service/api/things/1234.

You might try the ProxyErrorOverride directive, which should pass through the error as-is when set to off (the default, in most cases). — AfroThundr
– AfroThundr, Commented Apr 22, 2019 at 22:22
@AfroThundr That's exactly what I ended up doing. Turning it off allowed the settings I had inside the docker1 box to work properly. If you want to answer it properly I'll mark it as accepted. — Jem
– Jem, Commented Apr 24, 2019 at 8:58

AfroThundr · Accepted Answer · 2019-05-07 20:33:21Z

1

^{From my comment earlier:}

You might try the ProxyErrorOverride directive, which should pass through the error as-is when set to off (the default, in most cases).

edited May 7, 2019 at 20:33

answered Apr 24, 2019 at 13:51

AfroThundr

1,2652 gold badges20 silver badges30 bronze badges

Sign up to request clarification or add additional context in comments.

Collectives™ on Stack Overflow

Apache not passing through 404 error from API behind reverse proxy

1 Answer 1

Comments

Your Answer

Hot Network Questions

Collectives™ on Stack Overflow

1 Answer 1

Comments

Your Answer

Sign up or log in

Post as a guest

Related