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 case
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 domain
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 that
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.
>
> /js/index.php/x.js?f=prototype/prototype.js,prototype/validation.js,mage/adminhtml/events.js,mage/adminhtml/form.js
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.
https://gist.github.co
> 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 S
> 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?
>
> Yeah
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
