On Tue, Oct 16, 2018 at 09:23:33PM +0200, Stefan Müller wrote:
Hi there,
> 1. documentation
>Is there any additional document for the -c command. I find only:
> 1. http://nginx.org/en/docs/switches.html
That page indicates that "-c" means that this nginx instance uses this
named config
Hello!
On Wed, Oct 17, 2018 at 07:47:26PM +0500, Илья Шипицин wrote:
> On Wed, Oct 17, 2018, 6:25 PM Maxim Dounin wrote:
>
> > Hello!
> >
> > On Wed, Oct 17, 2018 at 05:12:31PM +0500, Илья Шипицин wrote:
> >
> > > привет!
> > >
> > > беру стоковый 1.15.5
> > > вот такой конфиг
> > >
> > >
On Wed, Oct 17, 2018, 6:25 PM Maxim Dounin wrote:
> Hello!
>
> On Wed, Oct 17, 2018 at 05:12:31PM +0500, Илья Шипицин wrote:
>
> > привет!
> >
> > беру стоковый 1.15.5
> > вот такой конфиг
> >
> > upstream root-upstream {
> > server 127.0.0.1:999 fail_timeout=3ms;
> > }
> >
> >
> > server {
привет!
беру стоковый 1.15.5
вот такой конфиг
upstream root-upstream {
server 127.0.0.1:999 fail_timeout=3ms;
}
server {
listen 80;
server_name localhost;
location / {
proxy_pass http://root-upstream;
}
}
и, собственно, вот
Hello,
On Wed, Oct 17, 2018 at 05:13:15AM -0400, drookie wrote:
> Hello,
>
> I did't find the answer in documentation, but am I right, assuming from my
> observation, that when the proxy_cache is enabled for a location, and the
> client requests the file that isn't in the cache yet, nginx
Hello,
I prepare patch on actual sources. Settings limit_rate and limit_rate_after
works good. Please make code review, our testing and merge to main branche.
Thank you
Miroslav Nový
Example of configration:
location / {
root /var/www/default/;
index index.html index.htm;
Hello,
I did't find the answer in documentation, but am I right, assuming from my
observation, that when the proxy_cache is enabled for a location, and the
client requests the file that isn't in the cache yet, nginx starts
transmitting this file only after it's fully received from the upstream ?
Hi,
according to https://trac.nginx.org/nginx/ticket/1022#comment:1 and in this
mailing list archives, when there is configuration reload, keep-alive
connections are closed.
Is there a way to "drain" them? What I would like to have is to provide
some hard limit in configuration (in seconds) to
Очень интерсно откуда всё таки пролетает
302 Found\r\n
посравнивал дамп трафика со стенда и с captiv portal на микротике..там
вот этого 302 Found ,только
Hypertext Transfer Protocol
HTTP/1.1 302 Hotspot login required\r\n
nginx -V
nginx version: nginx/1.14.0
built with OpenSSL 1.0.2n 7 Dec
