Re: Require 'www' for https://example.com

2013-03-22 Thread Igor Sysoev
On Mar 23, 2013, at 2:44 , openletter wrote: > I am setting up a server that will be for a B2B business, and I want the > whole site to be served as https://www.example.com/ > > I have gotten a certificate and https://www.example.com runs just fine, but > I can't figure out how to require https:/

Re: Require 'www' for https://example.com

2013-03-22 Thread António P . P . Almeida
On 22 Mar 2013 23h44 CET, nginx-fo...@nginx.us wrote: > I am setting up a server that will be for a B2B business, and I want > the whole site to be served as https://www.example.com/ > > I have gotten a certificate and https://www.example.com runs just > fine, but I can't figure out how to require

Re: Strange $upstream_response_time latency spikes with reverse proxy

2013-03-22 Thread Jay Oster
Hi again everyone! Just posting a status update (because I hate coming across old threads with reports of a problem I'm experiencing, and there is no answer!) What I've found so far is starting to look like a Linux kernel bug that was fixed for ipv6, but still remains for ipv4! Here's the relevant

Re: Require 'www' for https://example.com

2013-03-22 Thread kirpit
# www fix server { # www.example.com -> example.com #server_name www.example.com; #rewrite ^ $scheme://example.com$request_uri? permanent; # www.example.com -> example.com server_name example.com; rewrite ^ $scheme://www.example.com$request_uri? per

Require 'www' for https://example.com

2013-03-22 Thread openletter
I am setting up a server that will be for a B2B business, and I want the whole site to be served as https://www.example.com/ I have gotten a certificate and https://www.example.com runs just fine, but I can't figure out how to require https://www.example.com when a user tries to go to https://exam

403 Forbidden, Nignx

2013-03-22 Thread Yunior Miguel A.
Hello again: I am have public a redmine and other aplication with nginx the other aplication is make in php, the php aplication have a api direccion for some services, when i put the url of de aplication without the api all is fine and not hae problem, but when I try to access the application usin

Re: Simple question about proxy cache

2013-03-22 Thread John Moore
On 22/03/13 14:11, Maxim Dounin wrote: > This looks like valid regular expression (try pcretest if unsure), but > from maintainability point of view I would recommend to use multiple > normal prefix or exact match locations instead of trying to combine > them into a single regexp. Yes, you're

nginx/freebsd kern.maxbcache

2013-03-22 Thread Richard Kearsley
Hi I'm trying to tune 'kern.maxbcache' with hope of increasing 'vfs.maxbufspace' so that more files can be stored in buffer memory on freebsd 9.1 It's suggested to tune this value here http://serverfault.com/questions/64356/freebsd-performance-tuning-sysctls-loader-conf-kernel and here http:/

Re: Simple question about proxy cache

2013-03-22 Thread Maxim Dounin
Hello! On Fri, Mar 22, 2013 at 12:24:21PM +, John Moore wrote: > On 22/03/13 11:43, Maxim Dounin wrote: > > Hello! > > > > On Fri, Mar 22, 2013 at 11:18:50AM +, John Moore wrote: > > > > [...] > > > >> Actually, there is one final tweak I'd like. There are a number of > >> different locat

Re: Simple question about proxy cache

2013-03-22 Thread John Moore
On 22/03/13 11:43, Maxim Dounin wrote: > Hello! > > On Fri, Mar 22, 2013 at 11:18:50AM +, John Moore wrote: > > [...] > >> Actually, there is one final tweak I'd like. There are a number of >> different locations which I'd like to use the proxy cache for. I cannot >> repeat for each location th

Re: Simple question about proxy cache

2013-03-22 Thread Maxim Dounin
Hello! On Fri, Mar 22, 2013 at 11:18:50AM +, John Moore wrote: [...] > Actually, there is one final tweak I'd like. There are a number of > different locations which I'd like to use the proxy cache for. I cannot > repeat for each location the block where the cache log is defined (it > rig

Re: Simple question about proxy cache

2013-03-22 Thread John Moore
On 22/03/13 11:18, John Moore wrote: > > Actually, there is one final tweak I'd like. There are a number of > different locations which I'd like to use the proxy cache for. I cannot > repeat for each location the block where the cache log is defined (it > rightly complains about duplication). So I

Re: Simple question about proxy cache

2013-03-22 Thread John Moore
On 18/03/13 11:21, John Moore wrote: > On 17/03/13 23:08, Maxim Dounin wrote: >> Hello! >> >> On Sun, Mar 17, 2013 at 08:08:39PM +, John Moore wrote: >> >>> I've used nginx as a reverse proxy server for a long while but I've not >>> tried out the proxy cache until today, and I have to say I'm a

Re: How to make nginx establish persistent connections with squid?

2013-03-22 Thread Maxim Dounin
Hello! On Fri, Mar 22, 2013 at 05:25:15AM -0400, selphon wrote: > hi, > I use nginx as load balance and forward request to squid use http/1.1, the > topology is below: > > chrome ---> nginx(:80) ---> squid(:8080) ---> origin server(nginx :80) > > the nginx configuration: > upstream backend { >

Re: Too Many Redirects - CDN Rewrite Rule

2013-03-22 Thread Kiril Kalchev
Hi, What Peter said is correct the best way is to prepare your application for using CDNs. But I think for a quick workaround of the problem you can try to make another server to be used only from CDN. server { location ~* ^.+.(jpe?g|gif|css|png|js|ico)$ { rewrite ^ http://cdn.mydomain.c

Re: Too Many Redirects - CDN Rewrite Rule

2013-03-22 Thread Francis Daly
On Thu, Mar 21, 2013 at 06:48:43PM -0400, toddlahman wrote: Hi there, > The reply I received from NetDNA after supplying the same information as I > did here is as follows: > > "Too many redirects" is a legit message in this scenario - example: You are > redirecting domain.com/file.jpg TO cdn.do

How to make nginx establish persistent connections with squid?

2013-03-22 Thread selphon
hi, I use nginx as load balance and forward request to squid use http/1.1, the topology is below: chrome ---> nginx(:80) ---> squid(:8080) ---> origin server(nginx :80) the nginx configuration: upstream backend { server 192.168.13.210:80; keepalive 10; } server { listen 80 def