An easy way to solve this issue is to create a "allowmyip.conf" file and
include it anywhere you wish.
allowmyip.conf file :
allow 11.22.33.44
deny all;
Then in your server block :location ^~ /apc/ {
# Allow home
include /etc/nginx/allowmyip.conf;
}
This way it will be real easy to
Please disregard this post, the error has been identified.
Posted at Nginx Forum:
http://forum.nginx.org/read.php?2,257421,257422#msg-257422
___
nginx mailing list
nginx@nginx.org
http://mailman.nginx.org/mailman/listinfo/nginx
This is a new install of 1.6.2 on linux dedi (centOS). I have the following
in my nginx.conf file:
fastcgi_cache_path /dev/nginx-cache levels=1:2 keys_zone=WORDPRESS:10m
max_size=1024m inactive=60m;
When testing the configurations (nginx -t), I get the following error
message:
nginx: [emerg] "f
Hello,
Very sorry to reply on this thread again.
I have the same requirement, but I still can not get nginx to follow the
302 redirect as I want.
My configuration:
upstream backend {
server 10.255.199.60:1220;
}
server {
listen 1220;
server_name localhost;
Hi Valentin:
Are you talking about the same "push" as I am? HTTP/2, or at least SPDY,
had the ability to *push* content like CSS in advance of the request,
pushing content into the browsers cache *before* it needs it. I'm not
talking about long polling or other technology. I've only read about thi
Running SSL correctly goes deeper than just declaring ciphers, and at
the least I'd recommend using the more modern versions with ECDHE unless
there is a technical reason you cannot. That said:
ssl_prefer_server_ciphers on;
ssl_ciphers
AES256-SHA256:AES256-SHA:AES128-SHA256:AES128-SHA
Hello,
I need to configure my nginx web server with only specific ssl ciphers.
I need to use only this ciphers:
TLS_RSA_WITH_AES_256_CBC_SHA (0x0035)
TLS_RSA_WITH_AES_128_CBC_SHA (0x002f)
TLS_RSA_WITH_3DES_EDE_CBC_SHA (0x000a)
TLS_RSA_WITH_RC4_128_MD5 (0x0004)
TLS_RSA_WITH_RC4_128_SHA (0x0005)
TLS
Hi Francis,
I got a way more familar now with this nginx config files. It works fine for
me.
The only thing that I still not get figured out, is this FastCGI "Y" error.
It doesn't happen at the old webserver which is an apache/fastcgi
environment, but I cannot play around with this, because it is
---
Posted at Nginx Forum:
http://forum.nginx.org/read.php?2,257388,257404#msg-257404
___
nginx mailing list
nginx@nginx.org
http://mailman.nginx.org/mailman/listinfo/nginx
On Wednesday 18 March 2015 04:32:55 Mark Mielke wrote:
> I think the ability to "push" content,and prioritize requests are examples
> of capabilities that might require intelligence upstream, and therefore a
> requirement to proxy HTTP/2 upstream.
"Server push" doesn't require HTTP/2 for upstream
Hi on my local system i have configured rsyslog and nginx.
i want all error logs should to go to syslog over the port no : 10514
my configuration for rsyslog.conf is.:
it is running fine showing no error:, but when i run any page on local host
which is not there, the error are not appearing appaer
I tried siege a lot, but could never get it to really use all cores on the
server, I found the tool wrk much more useful for load testing.
On Mar 18, 2015 2:31 AM, "halozen" wrote:
> 2 nginx 1.4.6 web servers - ocfs cluster, web root inside mounted LUN
> from SAN storage
> 2 MariaDB 5.5 servers -
I think the ability to "push" content, and prioritize requests are examples
of capabilities that might require intelligence upstream, and therefore a
requirement to proxy HTTP/2 upstream. However, I expect much of this is
still theoretical at this point, and until there are actually upstream
server
A CDN was the exact reason i asked the question in the first place, at the
moment not even cloudflare offers spdy or http/2 for upstream servers ( they
use nginx and have spdy enabled ).
Seems to me like http/2 for upstream would make building a CDN / Accelerator
easier(or at least better) for alo
14 matches
Mail list logo
