{"id":1957,"date":"2017-08-24T14:23:38","date_gmt":"2017-08-24T08:53:38","guid":{"rendered":"https:\/\/pheonixsolutions.com\/blog\/?p=1957"},"modified":"2026-09-08T14:48:44","modified_gmt":"2026-09-08T09:18:44","slug":"setup-redirection-using-proxypass-proxyreversepass-apache","status":"publish","type":"post","link":"https:\/\/pheonixsolutions.com\/blog\/setup-redirection-using-proxypass-proxyreversepass-apache\/","title":{"rendered":"Setup redirection using Proxypass, proxyreversepass on apache"},"content":{"rendered":"
\n
\n
\n
\n

Introduction<\/h2>\n

As modern web applications continue to evolve, it has become increasingly common to run application services on non-standard ports such as 3000<\/strong>, 5000<\/strong>, 8000<\/strong>, or 8080<\/strong>. Frameworks like Node.js, Django, Flask, Spring Boot, and various API services often listen on these ports instead of directly serving traffic through ports 80<\/strong> (HTTP) or 443<\/strong> (HTTPS).<\/p>\n

While exposing these application ports directly to the internet may work, it is generally not considered a best practice. Doing so can create management challenges, complicate SSL\/TLS implementation, and expose internal application infrastructure unnecessarily.<\/p>\n

A better approach is to place Apache HTTP Server<\/strong> in front of the application and configure it as a reverse proxy<\/strong>. Apache receives incoming requests on standard web ports and transparently forwards them to the backend application. Users continue to access the website using the main domain name, while the backend application remains hidden behind Apache.<\/p>\n

This setup offers several advantages:<\/p>\n\n