Tag Info

Hot answers tagged

2

Your reverse proxy is supposed to be correcting the Host: header for you by default. That it doesn't do so is a bug and should be reported to its developer(s). From RFC 7230 section 5.4: When a proxy receives a request with an absolute-form of request-target, the proxy MUST ignore the received Host header field (if any) and instead replace it with the ...


1

How about the following kind of principle? Say it's mod_proxy, ensure ProxyTimeout and the ProxyPass connectiontimeout= (and probably retry=) is at least the maintenance time or the API client idle timeout. Then, before the maintenance, firewall all new connections on the backend, eg iptables -I INPUT -p tcp --syn --dport 8080 -j DROP. After the ...


1

fail_timeout from the NGINX documentation: Sets: the time during which the specified number of unsuccessful attempts to communicate with the server should happen to consider the server unavailable; and the period of time the server will be considered unavailable. So a setting of 5 would mean 10 seconds total (5 timing out, 5 waiting before contacting ...


1

Perhaps instead of having many locations, you could use regex to match a particular URI to your upstream application: location ~ /(app)(\d+) { proxy_pass http://127.0.0.1:808$2/$1$2; include static_file_config.conf; } You can see how it works here: https://regex101.com/r/sM3eS9/1


1

You are essentially describing the necessity for a reverse-proxy. In your particular scenario, you might want to set up a virtual host with a config similar to the following example: <VirtualHost *:80> ServerName your.domain.com ProxyPass / http://localhost:4848/ ProxyPassReverse / http://localhost:4848/ ProxyPreserveHost on ...


1

Activate mod_proxy and mod_proxy_http on apache. Configure mod_proxy to pass whatever url you like to your application, see mod_proxy documentation for examples.



Only top voted, non community-wiki answers of a minimum length are eligible