Inquisitor Host

Hi, I have server A, for A, behind a firewall, server B sites are servers B and I want when zadam house, so it asked the Web server to B, so nejakadomena.com from the Internet will go straight to the B server (through A) but it is so that when I read the manual proxy and
Code: [Select] medline ProxyPass / mirror / foo / http://backend.example.com/ ProxyPassReverse / mirror / foo / http://backend.example.com/ strange when I have dns A + / mirror / foo only me directed at beckend.example.com (or our B) but I want to I Do not specify a server and for nothing, just simply to redirect my requirements nejakadomena.com next to B, so that I am not entering an IP / DNS server + some way but at only house which belonged to page B thank you for your advice
Code: [Select] medline <VirtualHost *: 80> ServerName www.example.com ProxyRequests Off <Proxy *> Order deny, allow Allow from all </ Proxy> <Location /> ProxyPassReverse http://backend.example.com/ ProxyPass http://backend.example.com/ </ Location> </ VirtualHost> but I bet it is alleged that before you start with this so you have to significantly resolve security - whatever that means. Therefore recommends haproxy. Haproxy will listen to the server and the public IP on port 80 and according virtualhostov will send requests to localhost: 80, or B: 80th Proxy and apache can not run on the same port, so you gotta compel the apache to listen medline only on localhost, for example, or on another port.
Inquisitor Host
Quote: Nassir 28. 04. 2011, 17:09:57 but I bet it is alleged that before you start with this so you have to significantly medline resolve security - whatever that means. Therefore recommends haproxy. Haproxy will listen to the server and the public IP on port 80 and according virtualhostov will send requests to localhost: 80, or B: 80th Proxy and apache can not run on the same port, so you gotta compel the apache to listen only on localhost, for example, or on another port.
Any workloads and server B burden of poor A. A configuration is supposedly lends itself to attacks on any computer using server A. Manuals However, I previews "bad" Configuring him. Write to any fact from wherever spoke of mod_proxy is also discussed procedure: medline first addressed by making and then address the proxy. When haproxy is not a performance issue: their website indicating the tests which are forwarded able to C2D after 10Gbit kabli and 9,5Gbit, what would you beginning to be enough. For us it used to vyrtualhostov based routing, so that each requirement is present parses addresses and points to the correct machine. We solved as migration from the old server to the new "without tripping". In the overall load 0.5 server (apache, mysql, php, dns) is not haproxy seen in the graphs do.
I am not in this defection medline vobec but I would need the best and easiest solution. I tried classic reverse proxy and it goes quite nicely but the truth of the moment load is actually zero ... just transparently straightforward medline solution without further nastrovoj and obscurity, so I guess I look at it ... it haproxy haproxy can be detected in the future, firewalled we still have 5 servers, and so do with it some kind of load balancing is quite nice plus ...
Load balancing across HAProxy is the L3 level and not mistaken ... Through NGX, Apache, etc are addressed to L7 load balancing. You take for example session stickness ... For us, the specific Sesna directed only at konkrent pool of servers. As always everything is SSL and HAProxy not terminate it and therefore unaware of the battery Sesna one. Therefore, it is quite Desirable solution -> request -> Firewall -> L2 LoadBalancer -> L7 LoadBalancer -> App server since there is no need to solve some power would suffice L7 LB. Sample config NGX: upstream server {xxxxxxxx xxxxxxxx 80 weight medline = 300 srun_id = xxxxxxxx; server xxxxxxxx 80 weight = 400 srun_id = xxxxxxxx; server xxxxxxxx 80 weight = 400 srun_id = xxxxxxxx; server xxxxxxxx 80 weight = 500 srun_id = xxxxxxxx; server xxxxxxxx 80 weight = 500 srun_id = xxxxxxxx; # Jvm_route $ cookie_JSESSIONID reverse; } # Main HTTP redirect server {listen 80; server_name _; access_log /var/log/nginx/http.access.log; server_name_in_redirect off; location / {rewrite ^ (. *) https: // $ host $ 1 permanent;