Perhaps a dumb question, but if all you are going to do is return a 403, why not just do this filtering in the firewall by blocking the offending IP space. Yeah I know a server should always have some response, but it isn't like you would be the first person to just block entire countries. (I don
Hi All
I have implemented GEO IP blocking which is working just fine. I have the
settings you see below.
map $geoip_country_code $country_access {
"US" 0;
default 1;
}
server {
if ($country_access = '1') {
return 403;
}
I notice though
Hi Andrey,
Thanks a lot for the solution, it working great in our Prod. You saved my
day!!!.
On Fri, Aug 10, 2018, 8:46 PM Andrey Oktyabrskiy wrote:
> On 10.08.2018 15:17, Andrey Oktyabrskiy wrote:
> > ### /etc/nginx/inc/cors_options.inc
> > if ($request_method = 'OPTIONS') {
> >add_header
I understand the connection establish timer, write timer and read timer
should be setup and removed in order, but where is the write timer? are
there lines in the logs saying I'm going to send the bytes, the sending is
on-going, and the bytes has been sent out?
Posted at Nginx Forum:
https://foru
Hello!
On Wed, Apr 10, 2019 at 07:56:26PM +, liu yunbin wrote:
> # HG changeset patch
> # User Yunbin Liu yunbin...@outlook.com
> # Date 1554925873 -28800
> # Thu Apr 11 03:51:13 2019 +0800
> # Node ID 228b945cf5f8c30356fc5760f696e49545075f00
> # Parent a6e23e343081b79eb924da985a4149093
On Fri, Apr 12, 2019 at 08:51:05AM -0400, allenhe wrote:
> but it looks to me the timer was set for the write not the read,
If the request is sent and the response is not yet received, nginx schedules a
timer for proxy_read_timeout.
> also the
> subsequent message isn't telling the nginx was int
but it looks to me the timer was set for the write not the read, also the
subsequent message isn't telling the nginx was interrupted while sending the
request?
Posted at Nginx Forum:
https://forum.nginx.org/read.php?2,283735,283739#msg-283739
___
nginx
Hello Allen,
On Fri, Apr 12, 2019 at 06:01:14AM -0400, allenhe wrote:
> Hi,
>
> The Nginx hangs at proxying request body to the upstream server but with no
> error indicating what's happening until the client close the font-end
> connection. can somebody here help give me any clue? following is t
Most likely this is an issue with your PHP application. Try a simple
PHP code or a ready-made app like WordPress and see if you can recreate the
error.
On Fri, Apr 12, 2019 at 3:41 PM sharvadze
wrote:
> For some reason all the POST request are delayed for about 1 min. Here is
> my
> configurat
For some reason all the POST request are delayed for about 1 min. Here is my
configuration:
/etc/nginx/nginx.conf
sendfile on;
tcp_nopush on;
tcp_nodelay off;
keepalive_timeout 65;
types_hash_max_size 2048;
proxy_buffering off;
proxy_http_version 1.1;
proxy_set_header Connection "";
/etc/nginx/s
Hi,
The Nginx hangs at proxying request body to the upstream server but with no
error indicating what's happening until the client close the font-end
connection. can somebody here help give me any clue? following is the debug
log snippet:
2019/04/12 14:49:38 [debug] 92#92: *405 epoll add connecti
11 matches
Mail list logo
