On Friday 29 April 2016 10:26:39 locojohn wrote:
> Hello,
>
> As of recently, shortly after updating nginx to version 1.11.0, we started
> getting the following errors in the error log for our sites configured with
> HTTP/2 and SSL:
>
> 2016/04/29 14:54:12 [info] 22321#22321: *290 client sent str
Hello!
On Fri, Apr 29, 2016 at 6:18 AM, Pasi Kärkkäinen wrote:
>
> One question about the new "ngx.balancer" Lua API .. with quick look I didn't
> notice anything related to upstream healthchecks.. is this something you've
> been looking at improving, or is it out of scope for this module?
>
Ye
Francis,
Sorry it took so long, I've finally come back to this question.
The example you gave works great:
server {
listen 127.0.0.1:8088;
return 200 "listen 127.0.0.1:8088\n";
}
server {
listen 10.0.1.2:8088;
return 200 "listen 10.0.1.2:8088\n";
}
Sorry, this is version of nginx obtained directly from GIT master branch. I
believe in the sense of described behaviour, it is essentially the same as
1.10.0.
Posted at Nginx Forum:
https://forum.nginx.org/read.php?2,266525,266533#msg-266533
___
nginx
For reference, that snippet seem to have done the job.
I'm not redirecting them, I trash them though.
if ($args ~* "^param\%"){
access_log off;
return 410;
}
Posted at Nginx Forum:
https://forum.nginx.org/read.php?2,265514,266528#msg-266528
___
n
If you're from the apache world, nginx configuration if often
counter-intuitive.
Does the following help?
# To find location matching a given request, nginx first checks locations
defined
# using the prefix strings (prefix locations). Among them, the location with
the
# longest matching prefix i
Strange, cannot find 1.11.x
Maybe you mean 1.10.0?
root@NC-PH-0657-10:/usr/local/src/nginx# wget
http://nginx.org/download/nginx-1.11.0.tar.gz
--2016-04-29 10:53:26-- http://nginx.org/download/nginx-1.11.0.tar.gz
Resolving nginx.org (nginx.org)... 206.251.255.63, 95.211.80.227,
2001:1af8:4060:a
Hello,
As of recently, shortly after updating nginx to version 1.11.0, we started
getting the following errors in the error log for our sites configured with
HTTP/2 and SSL:
2016/04/29 14:54:12 [info] 22321#22321: *290 client sent stream with data
before settings were acknowledged while processin
Hi,
I have a case where a redirect for
word-hyphen
should take precendence over a proxy_pass with
word
only
both are inside location {} directives.
location ~ ^/word-hyphen{
return 301 https://bla/one/two/word-hyphen ;
}
location /word{
proxy_pass http://upstream/ ;
}
I just can't ge
Hi,
On Thu, Apr 28, 2016 at 12:38:18PM -0700, Yichun Zhang (agentzh) wrote:
> Hi folks
>
> We had a good time at our first bay area OpenResty meetup [1] last
> month. Now I'd like to share with you the video recordings and slides
> for our presentations:
>
>
> * Presentation "What's new in Open
OK. Thanks!
-Mensaje original-
De: nginx [mailto:nginx-boun...@nginx.org] En nombre de itpp2012
Enviado el: miércoles, 27 de abril de 2016 12:33
Para: nginx@nginx.org
Asunto: Re: Protect site with username and password
http://nginx.org/en/docs/http/ngx_http_auth_basic_module.html
Posted
Francis, your config did magic! Kudos...
However, I just wondering the cause for the redirect URL having two trailing
slashes "//" i.e. "http://archives.unam.edu.na//";? The links seem to work
though.
The two server blocks are as follows.
server {
listen 80;
listen 443 ssl;
server
12 matches
Mail list logo
