mod-proxy

DeviceA serves as a reverse-proxy and is supposed to forward requests as follows: 192.168.1.10/DeviceB ==> 192.168.1.20/index.html 192.168.1.10/DeviceC ==> 192.168.1.30/index.html Both index files are located under /var/www and are static "Hello world!" pages. The problem is that I can't access those files through DeviceA, but if I call a test service also running on DeviceC (listening on port 12345) everything works fine. Am I wrong saying that the web server on DeviceB, DeviceC should respond with index.html if a request comes in on port 80 ??? lighttpd.conf DeviceA @192.168.1.10 server

We're running a web app on Tomcat 6 and Apache mod_proxy 2.2.3. Seeing a lot of 502 errors like this: Bad Gateway! The proxy server received an invalid response from an upstream server. The proxy server could not handle the request GET /the/page.do. Reason: Error reading from remote server If you think this is a server error, please contact the webmaster. Error 502 Tomcat has plenty of threads, so it's not thread-constrained. We're pushing 2400 users via JMeter against the app. All the boxes are sitting inside our firewall on a fast unloaded network, so there shouldn't be any network problems.

I am running a WebApplication on a Servlet Container (port 8080) in an environment that can be accessed from the internet (external) and from company inside (intenal), e.g. http://external.foo.bar/MyApplication http://internal.foo.bar/MyApplication The incomming (external/internal) requests are redirected to the servlet container using an apache http server with mod_proxy. The configuration looks like this: ProxyPass /MyApplication http://localhost:8080/MyApplication retry=1 acquire=3000 timeout=600 Keepalive=On ProxyPassReverse /MyApplication http://localhost:8080/MyApplication I am now

Basically my scenario is that I have an internal website that requires a SINGLE hard-coded username and password to access (and this can't be turned off, only changed). I am exposing this website through a reverse proxy for various reasons (hiding the port, simplifying url, simplifying NAT, etc). However, what I would like to do is be able to use Apache to handle the authentication so that: I don't have to give out single password to everyone I can have multiple usernames and passwords using Apache's BasicAuth For internal users, I don't have to prompt for a password EDIT: Second part about