если есть возможность привязаться к к/л стандартной ошибке, например, для 404:
error_page 404 =527 /plugin.html
а так в nginx кажется не предусмотрена ошибка 527.
br,
Aziz.
> On 22 Mar 2018, at 15:54, Никита wrote:
>
>
> Добрый день.
>
> При попытке сделать вернуть
check the limit_req_module,
http://nginx.org/ru/docs/http/ngx_http_limit_req_module.html
our beloved and hugely useful search engines gave this:
https://www.nginx.com/blog/rate-limiting-nginx/
it’s not possible to manipulate limits with cli though.
br,
Aziz.
> On 15 Mar 2018, at 09:52,
Hi,
perhaps you should’ve explained your intention bit more in details, may be with
some functional schema.
As of my current understanding, you want something like port mirroring to
duplicate
your network traffic.
anyways, it’s out of scope of nginx, search for “port/traffic mirroring”.
by the way, there is easier solution to this (thanks to Ruslan Ermilov)
something like this:
map $http_ $disabled {
^.{65,} 1
}
location / {
if $disable {
return 404;
}
proxy_pass http://upstream;
}
br,
Aziz.
> On 6 Mar 2018, at 15:16, Aziz Rozyev <aroz...@ngi
Atilla,
man page quote is related to the Valery’s argument that fsync wont affect
performance, forget it.
It’s nonsense because you’re trying to solve the reliability problem at the
different level,
it has been multiple times suggested here already by maxim and Paul, that it’s
better
to
it’s not hardcoded afaik.
check output of nginx -T perhaps it’s defined error_log directive somewhere..
br,
Aziz.
> On 1 Mar 2018, at 23:40, Daniel wrote:
>
> Hello all,
>
> can someone please explain to me why the location /var/log/nginx/error
> log is hardcoded in
if=/dev/zero of=/writetest bs=8k count=61960
conv=fsync
61960+0 records in
61960+0 records out
507576320 bytes (508 MB) copied, 1.74482 s, 291 MB/s
br,
Aziz.
> On 1 Mar 2018, at 00:41, Aziz Rozyev <aroz...@nginx.com> wrote:
>
> Valery,
>
> may you please
moment when the data of certain specific file reaches the
> storage depends on numerous factors, for example, I/O contention.
> Consequently, the exact moment when the data of a file being uploaded reaches
> the storage can be only determined by executing fsync.
>
> val
>
&g
While it’s not clear why one may need to flush the data on each http operation,
I can imagine to what performance degradation that may lead of.
if it’s not a some kind of funny clustering among nodes, I wouldn't care much
where actual data is, RAM still should be much faster, than disk I/O.
well, as I’ve said try checking headers first, as per the following doc:
https://wiki.jenkins.io/display/JENKINS/Jenkins+behind+an+NGinX+reverse+proxy
it can be much complicated than just proxy_pass’ing.
regarding sub_fillter,
try getting rid of one of the sub_filters, probably the second one:
Hi,
compare the output of
curl -ivvv http://jenkins:8080
curl -ivvv http://localhost/jenkins
then
curl -iLvvv http://jenkins:8080
curl -iLvvv http://localhost/jenkins
pay attention on the cookie headers.
java based applications usually may set session cookies and you should
handle
Hi,
show your full config, usually there is no need to set variable like
$tomcatdomain,
proxy_pass http://tomcatdomain;
is enough.
br,
Aziz.
> On 22 Feb 2018, at 16:17, imrickysingh wrote:
>
> Hi guys,
>
> I am new to nginx and facing some problem with my
hit Agrawal <mohit3081...@gmail.com> wrote:
>
> Thanks Aziz for this, I get your point, but can we do awking in fluentd cons
> file ? Basically we are looking for realtime awking a nginx error log file,
> how heavy this would be according to you.
>
> On 10 January 2018
achieved. grok didn't work for me, I tried regex then it was able to
> segregate time , pid, tid, log_level and message. I also need message break
> up for above pattern
>
> On 10 January 2018 at 17:12, Aziz Rozyev <aroz...@nginx.com> wrote:
> Hi Mohit,
>
> check the sec
for access log, I am looking to
> format error.log which doesn't take log_format directive.
> Above example that I gave is just for nginx error logs.
>
> Thanks
>
> On 10 January 2018 at 15:26, Aziz Rozyev <aroz...@nginx.com> wrote:
> btw, after re-reading the your qu
btw, after re-reading the your questing, it looks like you need something like
logstash grok filter.
br,
Aziz.
> On 10 Jan 2018, at 11:45, mohit Agrawal wrote:
>
> Hi ,
>
> I am looking to parse nginx error log so as to find out which particular IP
> is throttled
is the 'log_format json’ is what you’re asking for?
http://nginx.org/en/docs/http/ngx_http_log_module.html#log_format
br,
Aziz.
> On 10 Jan 2018, at 11:45, mohit Agrawal wrote:
>
> Hi ,
>
> I am looking to parse nginx error log so as to find out which particular
Hi Wade,
At least provide the access/error log fragments, curl -ivvv <..> outputs
directly to the 3rd party service and via the nginx,
jmeter (if you use that) outputs would make sense. Also, it would be nice to
compare nginx configurations from the mac and linux.
Currently it’s barely
check docs:
http://nginx.org/en/docs/http/ngx_http_map_module.html
every directive description has a “Context” field, where you may find
in which configuration context you can put the directive.
regarding your questions, yes, you actually have to put it on the very top - in
‘http'
context.
br,
Hi
create 4 separate upstreams for each of these apaches,
create 4 locations, within each location block proxy_pass to appropriate
upstream.
avoid using sub_filters, they are mostly forrewriting bodies of html documents.
http {
# for phpadmin
upstream phpadminup {
server
> I'm going to mention this in the Digital Ocean help pages.
>
> I disabled selinx, but I have a book laying around on how to set it up.
> Eh, it is on the list.
>
> On Wed, 20 Dec 2017 14:17:18 +0300
> Aziz Rozyev <aroz...@nginx.com> wrote:
>
>> Hi,
&g
Hi,
have you checked this with disabled selinux ?
br,
Aziz.
> On 20 Dec 2017, at 11:07, li...@lazygranch.com wrote:
>
> I'm setting up a web server on a Centos 7 VPS. I'm relatively sure I
> have the firewalls set up properly since I can see my browser requests
> in the access and error
ния if-а.
>
> В идеале: собственно в виде backup_proto=http :) поскольку эта же задача
> максимально элегантно решалась через
>> upstream remote {
>> server remote;
>> server local backup;
>> }
> пока не появилось требование к https у upstream-а
>
> 16.12.17 22:
а вариант с 2 апстримами не подходит?
upstream remote_up {
remote_upstream:443;
}
upstream local_up {
localhost:7070;
}
map $http_x_some_header $remote {
“”0;
“default” 1;
}
if ($remote) {
proxy_pass https://remote;
}
proxy_pass http://local;
br,
Aziz.
> On 16 Dec
Hi,
try
1) curl -ivvv https:// to your upstreams.
2) add server :443 (if your upstreams accepting ssl connections on 443)
br,
Aziz.
> On 20 Nov 2017, at 20:46, shivramg94 wrote:
>
> I am trying to use nginx as a reverse proxy with upstream SSL. For this,
location / {
>include /usr/local/nginx/naxsi.rules.default;
>
>set $ruleSet $ruleSetCC;
>rewrite ^(.*)$ /$ruleSet$1 last;
> }
>
>
> It's always using naxsi.rules.default. If this line is removed it's not using
> any rules (pass-all).
>
At first glance config looks correct, so probably it’s something with naxi
rulesets.
Btw, why don’t you use maps?
map $geoip_coutnry_code $strictness {
default “strict";
CC_1“not-so-strict";
CC_2“not-so-strict";
# .. more country codes;
}
# strict and not-so-strict locations
at least you’re missing or (|) operator between
> TRUSTED_CC_2 and TRUSTED_CC_3
br,
Aziz.
> On 12 Nov 2017, at 14:03, Jean-Paul Hemelaar wrote:
>
> Hi!
>
> I'm using Nginx together with Naxsi; so not sure it this is the correct place
> for this post, but I'll
Леонид,
а вам не подходит вариант с auth_request и дополнительным скриптом? что-то
такое:
location / {
auth_request /auth-proxy;
add_header X-Client-Cert $ssl_client_cert;
proxy_pass http://backend;
proxy_set_header X-Client-Cert
на официальном сайте есть инструкции:
https://www.nginx.com/resources/wiki/start/topics/recipes/wordpress/
br,
Aziz.
> On 7 Jul 2017, at 18:01, Nadya wrote:
>
> Спасибо,что подсказали решение. Не мешало бы еще указать ссылки.
>
> Posted at Nginx Forum:
>
30 matches
Mail list logo