Re: peer closed connection in SSL handshake while SSL handshaking

Hello, Could your issue be caused by this bug . It looks like Ubuntu is not going to fix this bug in precise. Also see here . In th

Re: changes to ngx.arg[1] not getting reflected in final response

vamshi Wrote: --- > header_filter_by_lua ' > ngx.header.content_length = nil > ngx.header.set_cookie = nil > > if ngx.header.location then > local _location = ngx.header.location

Re: peer closed connection in SSL handshake while SSL handshaking

I forgot to mention that this is running on Ubuntu 12.04LTS, with nginx version: nginx/1.6.0. Posted at Nginx Forum: http://forum.nginx.org/read.php?2,251423,251424#msg-251424 ___ nginx mailing list nginx@nginx.org http://mailman.nginx.org/mailman/list

peer closed connection in SSL handshake while SSL handshaking

Hello, I am seeing an odd thing occur in the error logs. We are developing an API, and when our mobile devices first hit the nginx server after waking up, the mobile device is rejecting the ssl cert. In the logs, we see that the ssl handshake is being closed. [info] 1450#0: *16 peer closed connec

Re: How can the number of parallel/redundant open streams/temp_files be controlled/limited?

Lastly, is there any way to try to get proxy_store to work in combination with proxy_cache, possibly by enabling the completed temp_file to be saved as a proxy_store file within its uri logical path hierarchy, and the cache_file descriptor aliased to it, or visa versa? (As it's often nice to be

Re: How can the number of parallel/redundant open streams/temp_files be controlled/limited?

Thank you for your patience. I mistakenly thought the 5 second default value associated with proxy_cache_lock_timeout was the maximum delay allowed between successive responses from the backend server is satisfaction of the reverse proxy request being cached prior to the cache lock being releas

Re: No CORS Workaround - SSL Proxy

Hello Maxim, On 6/22/14, 7:32 AM, "Maxim Dounin" wrote: >If there is nothing in error logs, and you are getting 502 errors, >then there are two options: > >1. The 502 errors are returned by your backend, not generated by > nginx. > >2. You did something wrong while configuring error logs and/

Re: How can the number of parallel/redundant open streams/temp_files be controlled/limited?

Hello! On Tue, Jul 01, 2014 at 10:15:47AM -0400, Paul Schlie wrote: > Then how could multiple streams and corresponding temp_files > ever be created upon successive requests for the same $uri with > "proxy_cache_key $uri" and "proxy_cache_lock on"; if all > subsequent requests are locked to th

Re: dav and dav_ext, mp4 module, PROPFIND not working for files

On 01 Jul 2014, at 09:35, audvare wrote: > Roman Arutyunyan Wrote: > --- >> >> Currently nginx does not seem to be able to do what you want. If >> you’re ready to patch >> the source here’s the patch fixing the issue. >> >> diff -r 0dd77ef9f

Re: SSL slow on nginx

I am currently using 1024 bit dhparams for maximum compatibility Here is my ssllabs report : https://www.ssllabs.com/ssltest/analyze.html?d=filterbypass.me If i remove the DH from my cipher suites , will handshake simulation be still a success for all browsers listed in the ssllabs report above

Re: How can the number of parallel/redundant open streams/temp_files be controlled/limited?

Then how could multiple streams and corresponding temp_files ever be created upon successive requests for the same $uri with "proxy_cache_key $uri" and "proxy_cache_lock on"; if all subsequent requests are locked to the same cache_node created by the first request even prior to its completion?

Re: SSL slow on nginx

Hello! On Tue, Jul 01, 2014 at 03:10:07AM -0400, khav wrote: > Thanks Maxim and GreenGecko for the insights > > > The worker process does match my number of cpu cores (running on 8 cores > atm) Good. It may be also good idea to make sure you don't have multi_accept enabled, just in case. >

Re: How can the number of parallel/redundant open streams/temp_files be controlled/limited?

Hello! On Tue, Jul 01, 2014 at 08:44:47AM -0400, Paul Schlie wrote: > As it appears a downstream response is not cached until first > completely read into a temp_file (which for a large file may > require 100's if not 1,000's of MB be transferred), there > appears to be no "cache node formed"

Re: proxy_pass_header not working in 1.6.0

Hello! On Tue, Jul 01, 2014 at 02:33:54PM +0200, Lucas Rolff wrote: > Hmm, okay.. > > Then I'll go back to an old buggy version of nginx which gives me the > possibility to use the headers from Backend! You don't need to go back (and I doubt it will help) - if you don't want nginx to serve fil

Re: proxy_pass_header not working in 1.6.0

But if files was served from backend I would assume to see the $upstream_response_time variable in nginx would return other stuff than a dash in 1.4.4 Like this, using logformat: "$request"$status$body_bytes_sent"$http_referer""$http_user_agent"$request_time$upstream_response_time'; "GET /c

Re: proxy_cache not serving file from edge server !!

shahzaib1232 Wrote: --- > Our caching method is :- > > client > origin ---> edge. > This is not going to work as expected, you need client > edge ---> origin Where edge proxy-passes to origin when file is not in cache. Posted at Nginx

Re: How can the number of parallel/redundant open streams/temp_files be controlled/limited?

As it appears a downstream response is not cached until first completely read into a temp_file (which for a large file may require 100's if not 1,000's of MB be transferred), there appears to be no "cache node formed" which to "lock" or serve "stale" responses from, and thereby until the first "

Re: proxy_pass_header not working in 1.6.0

On Tuesday 01 July 2014 14:33:54 Lucas Rolff wrote: > Hmm, okay.. > > Then I'll go back to an old buggy version of nginx which gives me the > possibility to use the headers from Backend! > [..] It doesn't do this either. Probably, it just has different configuration or permissions which result

Re: proxy_pass_header not working in 1.6.0

Hmm, okay.. Then I'll go back to an old buggy version of nginx which gives me the possibility to use the headers from Backend! Best regards, Lucas Rolff On Tuesday, July 1, 2014, Maxim Dounin wrote: > Hello! > > On Tue, Jul 01, 2014 at 01:00:05PM +0200, Lucas Rolff wrote: > > > nginx: > > > >

Re: proxy_pass_header not working in 1.6.0

Hello! On Tue, Jul 01, 2014 at 01:00:05PM +0200, Lucas Rolff wrote: > nginx: > > curl -I http://domain.com/wp-content/uploads/2012/05/forside.png > HTTP/1.1 200 OK > Server: nginx > Date: Tue, 01 Jul 2014 10:42:06 GMT > Content-Type: image/png > Content-Length: 87032 > Last-Modified: Fri, 08 Mar

Re: proxy_cache not serving file from edge server !!

Our caching method is :- client > origin ---> edge. On Tue, Jul 1, 2014 at 4:57 PM, shahzaib shahzaib wrote: > We've an origin and edge server with nginx-1.6 . Origin web-server(Located > in U.S) is configured with nginx_geo_module and edge(Local ISP) is > configured with proxy_cache in or

proxy_cache not serving file from edge server !!

We've an origin and edge server with nginx-1.6 . Origin web-server(Located in U.S) is configured with nginx_geo_module and edge(Local ISP) is configured with proxy_cache in order to cache files from origin server and serve from their lately. We're using following method for caching with proxy_cache

proxy_pass_header not working in 1.6.0

Seems like its not possible to ude try_files together with proxy_pass_header So if that was a bug before that you could get the headers from Backend but still serve the file using nginx I don't know. All dynamic files which I send to Backend is having cache-control headers set. All static files

Re: proxy_pass_header not working in 1.6.0

You need to examine traffic over the wire between the proxy and the origin as you send a request from an outside client to the proxy. This will allow you to see if the origin is even returning the expected headers to the proxy, or if the proxy is seeing a different response than a direct client is.

Re: How can the number of parallel/redundant open streams/temp_files be controlled/limited?

Hello! On Mon, Jun 30, 2014 at 11:10:52PM -0400, Paul Schlie wrote: > Regarding: > > > In http, responses are not guaranteed to be the same. Each > > response can be unique, and you can't assume responses have to be > > identical even if their URLs match. > > Yes, but potentially unique does

Re: proxy_pass_header not working in 1.6.0

nginx: curl -I http://domain.com/wp-content/uploads/2012/05/forside.png HTTP/1.1 200 OK Server: nginx Date: Tue, 01 Jul 2014 10:42:06 GMT Content-Type: image/png Content-Length: 87032 Last-Modified: Fri, 08 Mar 2013 08:02:48 GMT Connection: keep-alive Vary: Accept-Encoding ETag: "51399b28-153f8"

Re: proxy_pass_header not working in 1.6.0

On Tuesday 01 July 2014 10:30:47 Lucas Rolff wrote: > I've verified that 1.4.4 works as it should, I receive the cache-control > and expires headers sent from upstream (Apache 2.4 in this case), > upgrading to nginx 1.6.0 breaks this, no config changes, nothing. > > But thanks for the explanatio

Re: proxy_pass_header not working in 1.6.0

I've been investigating, and seems like it's related to 1.6 or so - because 1.4.2 and 1.4.4 works perfectly with the config in the first email. Any that can possibly reproduce this as well? Best regards, Lucas R Robert Paprocki wrote: Can we move past passive aggressive posting to a public ma

Re: proxy_pass_header not working in 1.6.0

I've verified that 1.4.4 works as it should, I receive the cache-control and expires headers sent from upstream (Apache 2.4 in this case), upgrading to nginx 1.6.0 breaks this, no config changes, nothing. But thanks for the explanation Robert! I'll try investigate it further to see if I can fin

Re: proxy_pass_header not working in 1.6.0

Can we move past passive aggressive posting to a public mailing list and actually try to accomplish something? The nginx docs indicate the following about proxy_pass_header "Permits passing otherwise disabled header fields from a proxied server to a client." 'otherwise disabled header fields' ar

Re: proxy_pass_header not working in 1.6.0

On 1 Jul 2014 11:01, "Lucas Rolff" wrote: > > So.. Where is the thing that states I can't use proxy_pass_header cache-control, or expires? :))) The proxy_hide_header and proxy_pass_header reference docs. ___ nginx mailing list nginx@nginx.org http://ma

Re: proxy_pass_header not working in 1.6.0

So.. Where is the thing that states I can't use proxy_pass_header cache-control, or expires? :))) Maybe I'm just stupid Best regards, Lucas Rolff Jonathan Matthews wrote: On 1 Jul 2014 10:34, "Lucas Rolff" > wrote: > > Do you have a link to a documentation that ha

Re: proxy_pass_header not working in 1.6.0

On 1 Jul 2014 10:34, "Lucas Rolff" wrote: > > Do you have a link to a documentation that has info about this then? Because in the below link, and in http://wiki.nginx.org/HttpProxyModule#proxy_pass_header theres nothing about what it accepts. How about the doc you already found, and then the link

Re: proxy_pass_header not working in 1.6.0

Do you have a link to a documentation that has info about this then? Because in the below link, and in http://wiki.nginx.org/HttpProxyModule#proxy_pass_header theres nothing about what it accepts. Best regards, Lucas Rolff Jonathan Matthews wrote: On 1 Jul 2014 10:20, "Lucas Rolff"

Re: proxy_pass_header not working in 1.6.0

On 1 Jul 2014 10:20, "Lucas Rolff" wrote: > > Well, it used to work before 1.6.0.. > > For me http://nginx.org/en/docs/http/ngx_http_proxy_module.html#proxy_pass_header shows that I should do: > > proxy_pass_header Cache-Control; > > So that should be correct No. You have misread the documentatio

Re: proxy_pass_header not working in 1.6.0

Well, it used to work before 1.6.0.. For me http://nginx.org/en/docs/http/ngx_http_proxy_module.html#proxy_pass_header shows that I should do: proxy_pass_header Cache-Control; So that should be correct Best regards, Lucas Rolff Jonathan Matthews wrote: On 1 Jul 2014 07:58, "Lucas Rolff"

Re: proxy_pass_header not working in 1.6.0

On 1 Jul 2014 07:58, "Lucas Rolff" wrote: > > Hi guys, > > I'm currently running nginx version 1.6.0 (after upgrading from 1.4.4). > > Sadly I've found out, after upgrading proxy_pass_header seems to stop working, meaning no headers is passed from the upstream at all You need to read the proxy_pa

Re: SSL slow on nginx

Thanks Maxim and GreenGecko for the insights The worker process does match my number of cpu cores (running on 8 cores atm) How can i know the number of handshakes per seconds occurring on the server The openssl speed result have been posted on http://pastebin.com/hNeVhJfa for readability Yo