Hi Francis,
Thanks for the reply!
w.r.t. the "http://nginx.org/r/proxy_buffering;, the doc does not mention if
the buffering works for header, body or both, I'm wondering if nginx can
postpone the sending of upstream header in any ways? otherwise the client
will get wrong status code in this
On Thu, May 14, 2020 at 11:10:20AM -0700, PGNet Dev wrote:
Hi there,
> editing a general location match to exclude one, specific instance?
It is usually easier to use positive matches instead of negative ones.
> I've had a trivial 'protection' rule in place for a long time
>
> location
On Thu, May 14, 2020 at 03:37:38PM -0400, Amakesh wrote:
Hi there,
> Earlier Let’s encrypt certificates worked fine for for all of them, but
> recently installed Nginx as web proxy.
> https://www.ssllabs.com shows all of the certificates have Server
> hostname(rsvix170.gerwanserver.de) as
On Fri, May 15, 2020 at 01:51:13AM -0400, allenhe wrote:
Hi there,
> Will nginx buffer the header before receiving of the whole body?
> If not, what if error happens in the middle of body receiving? nginx has no
> chance to resend the error status then.
What do you want your nginx to do, in
On Fri, May 15, 2020 at 09:49:38AM -0700, Palvelin Postmaster wrote:
Hi there,
> I’m trying to learn how to pass specific Magento 1.x URLs such as this to a
> PHP-FPM backend.
>
>
I’m trying to learn how to pass specific Magento 1.x URLs such as this to a
PHP-FPM backend.
/js/index.php/x.js?f=prototype/prototype.js,prototype/validation.js,mage/adminhtml/events.js,mage/adminhtml/form.js,scriptaculous/effects.js
All the nginx configs I’ve found (e.g.
Помогите советом. Ну или хотя бы направлением.
Есть сервер nginx-proxy. За ним два сервера (х.4 и х.5) . Как
сделать чтобы шли запросы от с сервера .4 до х.5 по доменному имени
(без указания порта)?
location / {
proxy_pass http://хх.4;
proxy_set_header
> On 15 May 2020, at 12:43, Marko Domanović wrote:
>
> Long story short, I need nginx 0.7.65 to be able to support TLS1.2.
> Seems like it's dependent on openssh version and installed one is 1.0.1t
> which seem to support TLS1.2, but "nmap --script ssl-enum-ciphers -p 443
> sitename" says only
> it's dependent on openssh version and installed one is 1.0.1t
On openssl.
> which seem to support TLS1.2, but "nmap --script ssl-enum-ciphers -p 443
> sitename" says only SSLv3 and TLS1.0 are supported. So is there anything I
> can to to make nginx 0.7.65 recognize TLS1.2 and use it?
>
>
Long story short, I need nginx 0.7.65 to be able to support TLS1.2.
Seems like it's dependent on openssh version and installed one is 1.0.1t
which seem to support TLS1.2, but "nmap --script ssl-enum-ciphers -p 443
sitename" says only SSLv3 and TLS1.0 are supported. So is there anything
I can to to
Спасибо, чё то не подумал )
Posted at Nginx Forum:
https://forum.nginx.org/read.php?21,288040,288043#msg-288043
___
nginx-ru mailing list
nginx-ru@nginx.org
http://mailman.nginx.org/mailman/listinfo/nginx-ru
Hi All,
We are using proxy cache to cache the response from upstream for a day.
But, when the cache expires, API stops responding with 500.
Getting the error: open() "proxycachepath" failed (13: Permission denied)
On reloading the nginx, server is able to connect to upstream and cache
response
Блок server. Правила в отдельный файл и пользуйся include.
"milov" 15 мая 2020 г. 10:15:07 написал:
Нужно закрыть паролем поддомен, на if ругается, а location не получается
придумать
location ~ poddomen\.domen\.ru {
auth_basic "Private zone. Only for administrator!";
Нужно закрыть паролем поддомен, на if ругается, а location не получается
придумать
location ~ poddomen\.domen\.ru {
auth_basic "Private zone. Only for administrator!";
auth_basic_user_file /home/.htpasswd;
}
В отдельный блок server Неохота выносить т.к. там кучу других
14 matches
Mail list logo
