Re: Possible to overwrite a fastcgi_param "later", once a location block has already been closed?

On 7/9/2013 5:47 PM, Francis Daly wrote: > On Tue, Jul 09, 2013 at 04:48:27PM -0400, Ben Johnson wrote: > > Hi there, > >> I am working with a server configuration that is partly outside of my >> control, > > I suspect that that's not the intended use case for nginx. Whoever writes > the confi

Re: nginx cache loader process

Hello, Take a look at 'proxy_cache_lock' directive. -- Vil Surkin среда, 10 июля 2013 г. в 3:50, badtzhou написал: > We are running nginx 1.2.9. What will happen if cache loader is running. The > file on disk haven't been loaded into the cache zone yet and someone try to > access the same fi

Re: nginx cache loader process

We are running nginx 1.2.9. What will happen if cache loader is running. The file on disk haven't been loaded into the cache zone yet and someone try to access the same file. Will it cause any issue? How will it affect cache loader process. If I don't want any file on the disk to be loaded, can I

Re: Possible to overwrite a fastcgi_param "later", once a location block has already been closed?

On Tue, Jul 09, 2013 at 04:48:27PM -0400, Ben Johnson wrote: Hi there, > I am working with a server configuration that is partly outside of my > control, I suspect that that's not the intended use case for nginx. Whoever writes the config file has the opportunity to configure it not to start. >

Possible to overwrite a fastcgi_param "later", once a location block has already been closed?

Hello, I am working with a server configuration that is partly outside of my control, and have a need to overwrite a fastcgi_param "after" the directives that are outside of my control have already been included. The basics of the configuration are: --

Re: spdy per location

Thanks all I think I will just open another port (looks like 6121 is registered for spdy?) because I'm not using hostnames (only IPs) and I don't like redirects so: server {     listen 80;     listen 443 ssl;     listen 6121 ssl spdy

Re: Disable open_file_cache for a specific location

Yes, you are right. Such a small change! Thanks a lot and sorry for taking such a long time. Next time I know how to post a proper question. Posted at Nginx Forum: http://forum.nginx.org/read.php?2,240504,240687#msg-240687 ___ nginx mailing list nginx

Re: Dropped https client connection doesn't drop backend proxy_pass connection

Hello! On Tue, Jul 09, 2013 at 12:52:24PM +1000, Robert Mueller wrote: > > > I have the same problem. I really need this feature. how is this going? > > > > >> Maxim Dounin: > > > Valentin is already worked on this, and I believe he'll be able to > > > provide a little bit more generic patch. >

Re: $request_header_length and $request_body_length?

Hello! On Mon, Jul 08, 2013 at 10:20:08PM -0400, est wrote: > Hello, > > I am trying to diagnose a weird 408 error problem on nginx. > > My theory is that the client might be using some kind of crack making the > request body too short for Content-Length header, so nginx waits more data > and u

Permissions not working for upload module

I've recently created an RPM for Cent-Os 4 for NGINX 1.2.6 which includes the `nginx_upload_module version 2.2.0` When the files get uploaded they don't have correct permissions. They have the default user `rw permission` However included the `upload_store_access` with the correct permissions

Re: Removing a request header in an access phase handler

Hello! On Tue, Jul 09, 2013 at 12:13:37AM +0200, Jan Algermissen wrote: > Hi Maxim, > > thanks, question inline: > > On 08.07.2013, at 19:59, Maxim Dounin wrote: > > > Hello! > > > > On Mon, Jul 08, 2013 at 06:45:33PM +0200, Jan Algermissen wrote: > > > >> Hi, > >> > >> I developing a hand