Apparently, from what I gather, if a 503 is returned the browsers (Chrome/IE10 I've tested) don't parse css, even if they can access them. I've verified this by typing the direct URL to the CSS file hosted on Nginx. I'm positive my code (HTML/CSS) is right. So how does one redirect to a page hosted on Nginx acting as a reverse proxy when the backend servers are down, while preserving CSS?by mevans336 - Nginx Mailing List - English
Hello Everyone, I am attempting to configure an internal redirect for any 502/503 errors in the event our backend servers are down. Here is the relevant part of my configuration: location / { add_header X-Frame-Options SAMEORIGIN; proxy_set_header Host $host; proxy_set_header X-Real-IP $remote_addr; proxy_set_header X-Forwby mevans336 - Nginx Mailing List - English
Is there any way to configure Nginx to fire off a script or otherwise send some type of notification when an HTTP error code is returned?by mevans336 - Nginx Mailing List - English
Thank you Jérôme. Our previous load balancers (Kemp Loadmasters) used the cookie method and it worked out well. We don't currently build Nginx from source however, but rather we use the Ubuntu apt packages, so it would require a little work on our side to change this. If anyone has suggestions that are native to Nginx, I would like to hear those as well. Cheers, Mattby mevans336 - Nginx Mailing List - English
Hello Everyone, We are currently using Nginx 1.2.1 to terminate SSL and to load balance between two JBoss servers. Here is my upstream block: upstream jboss_servers { ip_hash; server 192.168.1.100:8080; server 192.168.1.101:8080; } The issue we're having is such -- When a user is connected to Nginx, Nginx will proxy the connection to one of the two backend servers, for example 19by mevans336 - Nginx Mailing List - English
Hi Javi, Thank you, that appears to have worked perfectly. Javi Lavandeira Wrote: ------------------------------------------------------- > Hi, > > How about changing this: > > > rewrite ^ https://$server_name$request_uri? > permanent; > > To this: > > > rewrite ^ https://$server_name/home$request_uri? > permanent; > > > Iby mevans336 - Nginx Mailing List - English
Hello Gents, Right now, we catch all http://www.domain.com requests and do a simple rewrite to https://www.domain.com. I would like to update this re-write to point to https://www.domain.com/home. Here is my server section for the non-SSL (http) server: server { listen 192.168.1.1:80; server_name www.domain.com; location / { add_heaby mevans336 - Nginx Mailing List - English
Thank you Sergey. I'll probably just wait and upgrade to 12.04 and 1.2.1 at the same time.by mevans336 - Nginx Mailing List - English
Hello, I have the correct variables enabled in my sites-available/default and ssllabs reports that TLS v1 is available, but TLS v1.1 and TLS v1.2 are not: ssl_protocols TLSv1.1 TLSv1.2 TLSv1 SSLv3; ssl_ciphers RC4:HIGH:!aNULL:!MD5; ssl_prefer_server_ciphers on; I am using the pre-built nginx 1.2 packages from 'deb http://nginx.org/packages/ubuntu/ oneiric nginx' anby mevans336 - Nginx Mailing List - English
That makes perfect sense, thank you Cliff.by mevans336 - Nginx Mailing List - English
Francis, Thank you for the wonderfully detailed response. I have printed your reply to PDF for safekeeping as you covered many things I didn't know curl was even capable of. You also provided me a much deeper understanding of the HTTP redirect process. I am extremely thankful for both. Cheers, Mattby mevans336 - Nginx Mailing List - English
Cliff Wells Wrote: ------------------------------------------------------- > On 03/06/2012 02:06 PM, Francis Daly wrote: > > My guess is that "first contact" information is > not shared between the > > two jboss servers, so if serial requests from a > single client don't > > always go to the same server, bad things happen. > You should be able toby mevans336 - Nginx Mailing List - English
Cliff, The application performs a redirect because that was the way it was originally designed. It uses the ACEGI security framework. I have turned the ACEGI HTTP -> HTTPS redirect off with the same behavior however. After my post, I stumbled across the ip_hash upstream variable and that has resolved the issue. Or at least, masked it and made things functional. I am aware that Nginx isby mevans336 - Nginx Mailing List - English
I have an Nginx reverse-proxy sitting in front of two JBoss servers. If I attempt to add the second JBoss server to the upstream directive, I receive an Error 310 (net::ERR_TOO_MANY_REDIRECTS) from Chrome, IE just displays an "Internet Explorer cannot display this webpage" error. If I comment the second upstream server out a kill -HUP the master process, everything works properly. I aby mevans336 - Nginx Mailing List - English
Hello Everyone, I am deploying two Nginx servers running on Ubuntu with heartbeat for HA/fail-over. Each server has two physical NIC interfaces. In my firewall, I have 1:1 NAT mappings from the various public IP addresss to a NAT subnet that Nginx is listening on. The NAT interface (LAN) from the firewall is plugged into the same switch (same subnet, VLAN) as my two Nginx servers. I have theby mevans336 - How to...
Thanks Ryan, that did it. Any other tips for nginx and JBoss/Tomcat?by mevans336 - Nginx Mailing List - English
Hello, I am working on replacing our Kemp Loadbalancers with nginx and so far, things look good except for a minor issue. When a request comes into my server on the HTTP port, our JBoss server uses ACEGI to redirect to https://www.myserver.com/dev/home. The first time this redirection occurs, I'm sent to the URL of my proxy_pass directive. I am running version 0.7.65 stable on CentOS 5.4. Heby mevans336 - Nginx Mailing List - English