mod-proxy

How to configure mod_proxy to block every site except one

▼魔方 西西 提交于 2020-01-13 02:16:12
问题 I'm trying to set up mod proxy to block all traffic except to a specific domain. I can configure it to block individual domains using the ProxyBlock directive, and I can block everything using ProxyBlock *. Is there a way to block everything but one domain? Thanks, -Andrew 回答1: On apache 2.2 you need to have 2 proxy sections. ProxyRequests On ProxyVia On # block all domains except our target <ProxyMatch ^((?!www\.proxytarget\.com).)*$> Order deny,allow Deny from all </ProxyMatch> # here goes

Reverse proxy with websocket mod_proxy_wstunnel

生来就可爱ヽ(ⅴ<●) 提交于 2020-01-10 18:45:54
问题 I have a problem with the web sockets and my reverse proxy Apache, I have upgraded in latest release 2.4.5 and loaded the module mod_proxy_wstunnel . The httpd.conf : <VirtualHost *:80> ServerAdmin webmaster@localhost ServerName www.toto.fr ServerAlias toto.fr ProxyPass /my_app http://1X.X.X.1:8080/my_app ProxyPassReverse /web_pmr http://1X.X.X.1:8080/my_app ProxyPassReverseCookiePath /my_app / ProxyPassReverseCookieDomain localhost my_app ProxyRequests off ProxyTimeout 15 #WEBSOCKETS

Reverse proxy with websocket mod_proxy_wstunnel

▼魔方 西西 提交于 2020-01-10 18:44:18
问题 I have a problem with the web sockets and my reverse proxy Apache, I have upgraded in latest release 2.4.5 and loaded the module mod_proxy_wstunnel . The httpd.conf : <VirtualHost *:80> ServerAdmin webmaster@localhost ServerName www.toto.fr ServerAlias toto.fr ProxyPass /my_app http://1X.X.X.1:8080/my_app ProxyPassReverse /web_pmr http://1X.X.X.1:8080/my_app ProxyPassReverseCookiePath /my_app / ProxyPassReverseCookieDomain localhost my_app ProxyRequests off ProxyTimeout 15 #WEBSOCKETS

ProxyPass Failing

我的未来我决定 提交于 2020-01-05 07:27:09
问题 I have a new rasperryPi webserver running raspbian that I'm trying to use to proxy to web-enabled device from FieldServer Tech (fieldserver.com) on our intranet. Inside /etc/apache2/sites-available/default I've added the following line: <Location /modbus/> ProxyPass http://192.168.10.124/ </Location> After restarting the webserver when I try to browse to the defined proxy address http://192.168.10.7/modbus/ I get the password prompt from the FieldServer device but after authenticating I get

ProxyPass Failing

一世执手 提交于 2020-01-05 07:26:06
问题 I have a new rasperryPi webserver running raspbian that I'm trying to use to proxy to web-enabled device from FieldServer Tech (fieldserver.com) on our intranet. Inside /etc/apache2/sites-available/default I've added the following line: <Location /modbus/> ProxyPass http://192.168.10.124/ </Location> After restarting the webserver when I try to browse to the defined proxy address http://192.168.10.7/modbus/ I get the password prompt from the FieldServer device but after authenticating I get

Explain CouchDB's serving of websites, is CouchDB bundled somehow with Apache and how does it work?

▼魔方 西西 提交于 2019-12-25 08:14:11
问题 I am trying to understand how CouchDB work. Does it come bundled up with separate Apache or does it use the Apache in the system. I am trying to understand how it determines where to serve the site and how are different directions done. This is important information because I am trying to understand how to implement the Apache 2.2 mod-proxy -module here with it. Do I need to tune CouchDB or do I need to tune a separate Apache process? Suppose you have 10 CouchDB processes and you want to

accessing the web2py admin interface via wsgi

对着背影说爱祢 提交于 2019-12-25 02:18:41
问题 The web2py book states The administrative interface, admin, is only accessible from localhost unless you run web2py behind Apache with mod_proxy. If admin detects a proxy, the session cookie is set to secure and admin login does not work unless the communication between the client and the proxy goes over HTTPS; this is a security measure. All communications between the client and admin must always be local or encrypted; otherwise an attacker would be able to perform a man-in-the middle attack

I can't seem to get mod_proxy_html working at all - no debug output, no errors

半城伤御伤魂 提交于 2019-12-25 01:49:38
问题 I'm running apache 2.0.52, and I've compiled the mod_proxy_html module (version 3.1), apache starts fine, no errors. The only problem is that the module appears to do nothing - I'm not even getting any debugging output in the error log, so I'm a little stumped, as I fdon't even have any logging to point at a clue why it isn't working. The proxying itself works fine, but there's no url modification going on. Here's the snippet from my httpd.conf file: ProxyHTMLEnable On ProxyHTMLLogVerbose On

apache mod_proxy tomcat remove 8443

て烟熏妆下的殇ゞ 提交于 2019-12-25 01:14:52
问题 I put apache in front of tomcat using mod_proxy. The apache is listening on port 80, and when I access from www.example.com the apache redirect to port 8080 wich tomcat is listening, and tomcat redirect to port 8443. The problem is the address bar show https://www.example.com:8443. How I remove the :8443 from the address bar? Apache virtualhost config <VirtualHost *:80> ProxyPreserveHost On ProxyRequests Off ServerName www.example.com ServerAlias example.com ProxyPass / http://localhost:8080/

Apache mod_rewrite and multiple domains

孤人 提交于 2019-12-23 03:13:11
问题 I'm trying to use mod_rewrite to map multiple domains to different servlets on one host. Example: www.dom1.com -> 192.168.1.n/dom1 www.dom2.com -> 192.168.1.n/dom2 ... I'm using the mod_rewrite and mod_proxy and VirtualHost directive but it seems that the reverse mapping via ProxyPassReverse doesn't work as I expected. ProxyPassReverse /subdomain.domain.com http://192.168.1.n/subdomain doesn't work. I've turned rewrite-logging on with RewriteLog /var/log/rewrite.log From the logs I'd say that