Reverse Proxy Deployment

Deploy behind Apache reverse proxy by creating ProxyPass configuration files in /etc/apache2/proxy-conf.d with proper path stripping, ordering API routes before frontend routes, using relative URLs in your application, and reloading Apache to apply changes.

ProxyPass rules must define API routes before frontend routes to prevent the frontend catch-all from intercepting API requests. Apache processes rules sequentially, so order determines which service handles each incoming request.

Relative URLs ensure your frontend correctly routes through the reverse proxy's base path without hardcoding the internal service location, allowing the proxy to transparently handle path rewriting and multiple deployment contexts.

Trailing slash handling in ProxyPass affects whether requests match rules and how paths are stripped. Consistent trailing slash placement across your proxy config and application routes prevents routing mismatches and request failures.

Yes, test locally by creating your Apache config in proxy-conf.d, reloading Apache, and verifying both internal and external access to API and frontend routes work correctly before deploying to rivsprod01.