> > proxy_set_header SWSSLHDR $server_port; > > > > nice catch! But once again, because HTTP_REQUEST is client-side, so > says this F5-certified engineer with reference to the docs, it should > be $proxy_port instead of $server_port. Thanks to everyone that responded to my questions. Nginx has a great community around it! It has become clear that I need to learn morby w.b - Nginx Mailing List - English
peter wrote on 03/19/2013 01:54:20 PM: > You might find that you get most traction with open resty ? its an > nginx bundle project that includes ngx_lua, > HttpHeadersMoreModule and a bunch of other mopdules that are great > for transforming requests > and implementing F5-like logic. I have been using it for six months > and its saved me a bunch of time > and helped me geby w.b - Nginx Mailing List - English
Peter Booth wrote on 03/19/2013 10:43:12 AM: > The code does the following: > > 1. remove an HTTP header named "SWSSLHDR" > 2. replaces it with SWSSLHDR: port, where the port is the local port of > the "current context's TCP connection", presumably the port that your F5 > virtual server is listening on. I had somewhat figured that out. It isn't clear fromby w.b - Nginx Mailing List - English
I am configuring Nginx to sit in front of several IIS web servers to do load balancing and SSL signing. THe IIS application is supplied by an outside vendor. I have the load balancing and SSL signing working, with one exception. The login page doesn't work. :( When the vendor hosts this application, they use F5 hardware for SSP and load balancing. They gave me thisrule that they use inby w.b - Nginx Mailing List - English
From: "Camayoc" <nginx-forum@nginx.us> > I'd argue the commercial solutions are value for money, given the > complexities. Not to mention most organizations that would need such a device like having someone to hold accountable (usually via lawsuit) when it fails. Confidentiality Notice: This electronic message and any attachments may contain confidential or privilegeby w.b - Nginx Mailing List - English
> From: "Reddirt" <nginx-forum@nginx.us> > I got past that error and now the nginx error log has this: > > 2013/03/14 14:22:10 1537#0: *1 connect() failed (111: Connection > refused) while connecting to upstream, client: 192.168.20.3, server: , > request: "GET / HTTP/1.1", upstream: "http://127.0.0.1:3000/", host: > "ndeavor.ameiproby w.b - Nginx Mailing List - English
From: "Reddirt" <nginx-forum@nginx.us> > bitnami@linux:/opt/bitnami$ sudo ./ctlscript.sh start nginx > nginx: invalid host in upstream "127.0.0.1:3000/ndeavor" in > /opt/bitnami/nginx/conf/vhosts/ndeavor.conf:2 What is your upstream section of the configuration file? Do you have the "/ndeavor" as part of the server statement? Try taking itby w.b - Nginx Mailing List - English
> > Dump question, but why did you put the vhost-files into "conf.d"? > > Normally > > they are stored in "sites-available" and symlinked in "sites-enabled". > > nginx > > (as apache) uses this directory to read all information about the vhosts. > > Are there any templates in "sites-enabled"? How do they look like? &gby w.b - Nginx Mailing List - English
Maxim wrote on 02/06/2013 11:47:22 AM: > The ip_hash balancing was designed to work with internet services, > and use of /24 networks allows it to keep users from migrating > between backend servers as they get new IP address on > reconnect/reboot (typically from the same /24 network, at least at > the time ip_hash was introduced) while still providing good > distribution bby w.b - Nginx Mailing List - English