Re: nginx 1.11.0: client sent stream with data before settings were acknowledged while processing HTTP/2 connection

2016-04-30 Thread itpp2012
eiji-gravion Wrote: --- > I'm seeing the same thing happen in Firefox 46. Nb. there is currently an issue with 46 and TLS. ea. don't use 46 for testing. Posted at Nginx Forum: https://forum.nginx.org/read.php?2,266525,266551#msg-266551 ___

Re: nginx 1.11.0: client sent stream with data before settings were acknowledged while processing HTTP/2 connection

2016-04-30 Thread eiji-gravion
I'm seeing the same thing happen in Firefox 46. Posted at Nginx Forum: https://forum.nginx.org/read.php?2,266525,266550#msg-266550 ___ nginx mailing list nginx@nginx.org http://mailman.nginx.org/mailman/listinfo/nginx

Re: nginx 1.11.0: client sent stream with data before settings were acknowledged while processing HTTP/2 connection

2016-04-30 Thread locojohn
Valentin V. Bartenev Wrote: > This issue should be reported to Safari. It appears that it doesn't > handle refused streams. > > I'm going to make a workaround, but it will take time. Thank you Valentin! Let me know when the workaround is in the trunk so I could get it form the repository and r

Re: Trailing Slash redirection poblem

2016-04-30 Thread Francis Daly
On Sat, Apr 30, 2016 at 12:47:20PM +0500, Muhammad Yousuf Khan wrote: Hi there, > I have been trying to remove the trailing slash with this redirection rule. > rewrite ^/(.*)/$ /$1 permanent; > > however it is creating a loop. > > curl -I https://.com/live/ > > HTTP/1.1 301 Moved Permanent

Re: Nginx servers on both *:80 and :80? also duplicate listen parameters error when binding by just specific ips

2016-04-30 Thread Francis Daly
On Fri, Apr 29, 2016 at 05:12:44PM -0400, CJ Ess wrote: Hi there, > Where I get into problem is if I do something like this: > > server { > listen 127.0.0.1:8088 backlog=65536 deferred; > return 200 "listen 127.0.0.1:8088\n"; > } > server { > listen 10.0.1.2:8

Trailing Slash redirection poblem

2016-04-30 Thread Muhammad Yousuf Khan
Dear All, Need some help to remove trailing Slash. I have been trying to remove the trailing slash with this redirection rule. rewrite ^/(.*)/$ /$1 permanent; however it is creating a loop. curl -I https://.com/live/ HTTP/1.1 301 Moved Permanently Server: nginx/1.6.2 Date: Sat, 30 Apr 2016 0

Re: Permanent Redirect on nginx

2016-04-30 Thread Francis Daly
On Fri, Apr 29, 2016 at 07:33:04AM +, Mumanyi, Bravismore wrote: Hi there, > Francis, your config did magic! Kudos... Good to hear you have it working, thanks. > However, I just wondering the cause for the redirect URL having two trailing > slashes "//" i.e. "http://archives.unam.edu.na//"