mod-proxy

I need to set up a proxy with authentication to verify the behavior of an application that connects to the internet. I am trying to set-up an Apache installation with forward proxy and authentication, and even though I am close to make it work, I wonder if there is maybe a better way, as the configuration is fairly esoteric. How can Apache be configured to work this way? Is there any other good option that is already configured? Maybe some VM or some other software tool, instead of Apache? Mario Ortegón For the record, this is how I set up apache to be used as a forward-proxy with basic

Note: Updated config and added trailing slash to websocket path. Still same problem Is it possible to use go-websocket behind a Apache reverse proxy with mod_proxy_wstunnel ? I tried and failed to get things working. I tried to use the Chat example behind an Apache reverse proxy (with mod_proxy_wstunnel enabled). And it doesn't work. The proxy is a success, while the websocket part does not work at all. My Apache config looks similar to this: <VirtualHost *:80> DocumentRoot /var/www/foobar ServerName foobar.com ProxyPass / http://localhost:8080/ ProxyPassReverse / http://localhost:8080/

Problem: I need to host a Node-application and a php-application on the same server on different domains. example.com should use port 80 as normal, but node-example.com should route to port 3000. Routing ALL traffic from port 80 to 3000 works fine using mod_proxy, thusly: <VirtualHost *:80> ServerAdmin info@node-example.com ServerName node-example.com ServerAlias www.node-example.com ProxyRequests off <Proxy *> Order deny,allow Allow from all </Proxy> <Location /> ProxyPass http://localhost:3000/ ProxyPassReverse http://localhost:3000/ </Location> </VirtualHost> This however makes both example

Is there any way I connect Apache to Tomcat using an HTTP proxy such that Tomcat gets the correct incoming host name rather than localhost? I'm using this directive in apache: ProxyPass /path http://localhost:8080/path But it comes through as localhost, which is useless when we have a bunch of sites on the same server. I could set the host manually in the server config: <Connector port="8080" protocol="HTTP/1.1" connectionTimeout="20000" proxyName="pretend.host" proxyPort="80" /> But that again doesn't serve more than one site. And I don't like the idea of using a different internal port for

I have an Apache running that is only accessible via HTTPS. I want to serve websockets from an additional server application which runs on the same machine, but since it is not possible for clients to connect on another port than 443 to our server, those websocket connections need to be proxied through the Apache. Now, I've installed mod_proxy and configured it as follows: SSLProxyEngine on ProxyPass /ws https://127.0.0.1:9001 This does not work however. I can connect to https://server/ws in my browser now, but the apache seems to swallow part of the websockets headers, so that real websocket

What are the advantages and disadvantages of using mod_jk and mod_proxy for fronting a tomcat instance with apache? I've been using mod_jk in production for years but I've heard that it's "the old way" of fronting tomcat. Should I consider changing? Would there be any benefits? A pros/cons comparison for those modules exists on http://blog.jboss.org/ mod_proxy * Pros: o No need for a separate module compilation and maintenance. mod_proxy, mod_proxy_http, mod_proxy_ajp and mod_proxy_balancer comes as part of standard Apache 2.2+ distribution o Ability to use http https or AJP protocols, even

Summary: Apache 2.4's mod_proxy does not seem to be passing the Authorization headers to PHP-FPM. Is there any way to fix this? Long version: I am running a server with Apache 2.4 and PHP-FPM. I am using APC for both opcode caching and user caching. As recommended by the Internet, I am using Apache 2.4's mod_proxy_fcgi to proxy the requests to FPM, like this: ProxyPassMatch ^/(.*\.php)$ fcgi://127.0.0.1:9000/foo/bar/$1 The setup works fine, except one thing: APC's bundled apc.php, used to monitor the status of APC does not allow me to log in (required for looking at user cache entries). When I

I've managed to extend TokenAuthentication and I have a working model when using the request session to store my tokens, however when I attempt to pass Authorization as a header parameter as described here , I noticed that my Responses come back without the META variable HTTP_AUTHORIZATION. I also noticed that if I pass "Authorization2" as a header parameter that it is visible in the request: { '_content_type': '', 'accepted_media_type': 'application/json', '_request': <WSGIRequest path:/api/test_auth/, GET:<QueryDict: {}>, POST:<QueryDict: {}>, COOKIES:{ 'MOD_AUTH_CAS_S':