On Mon, Aug 24, 2015 at 9:48 PM, Ravikiran Chaulwar <
ravikiran.chaul...@elab.abudhabi.ae> wrote:
>
> We are planning to upgrade our apache web server in production from 2.2.15
> to 2.2.24. According to the documentation below steps are described -
> http://httpd.apache.org/docs/2.2/install.html
>
On Mon, Aug 24, 2015 at 9:52 PM, Steven Shi wrote:
> I have looked at and tried using the ProxyPassReverse directive.
>
> So the app communicates with the back end over port 2000. Any requests
> the app makes are sent to localhost:2000/foo to be processed by the back
> end.
>
> Currently the rel
Dear Team,
We are planning to upgrade our apache web server in production from 2.2.15 to
2.2.24. According to the documentation below steps are described -
http://httpd.apache.org/docs/2.2/install.html
To upgrade across minor versions, start by finding the file config.nice in the
build directo
I have looked at and tried using the ProxyPassReverse directive.
So the app communicates with the back end over port 2000. Any requests the
app makes are sent to localhost:2000/foo to be processed by the back end.
Currently the relevant configuration is
ProxyPass /app http://localhost:2000
Prox
On Mon, Aug 24, 2015 at 8:30 PM, Steven Shi wrote:
> I'm trying to proxy /app to localhost:2000 (where the app is hosted).
> Unfortunately, whenever the app makes a GET/POST request, the port 2000 is
> lost and the request is made to localhost:80 rather than localhost:2000.
>
> I feel as if the s
I'm trying to proxy /app to localhost:2000 (where the app is hosted).
Unfortunately, whenever the app makes a GET/POST request, the port 2000 is
lost and the request is made to localhost:80 rather than localhost:2000.
I feel as if the solution is something simple but I haven't been able to
discove
