It would be nice to avoid the overhead of getting
the ENV.
> On Jan 8, 2017, at 11:31 AM, Eric Covener wrote:
>
> We have an issue in proxy_fcgi in 2.4.21 and later that makes me think
> we need to tell proxy_fcgi when it's talking to php-fpm vs. a generic
> fastcgi application, due to historica
On Sun, 2017-01-08 at 11:31 -0500, Eric Covener wrote:
I'm easy either way.
> I notice that even complex proxy submodules (proxy_http) have no
> directives but use envvars for config. I actually like this approach
> for obscure-ish things, but directives do have some benefits (error
> checking,
We have an issue in proxy_fcgi in 2.4.21 and later that makes me think
we need to tell proxy_fcgi when it's talking to php-fpm vs. a generic
fastcgi application, due to historical things in httpd and php-fpm.
Basically, we cleaned up some fcgi variables that php-fpm was
interpreting as not only Apa
Am 08.01.2017 um 11:01 schrieb Stefan Eissing:
There is the reverse situation which is called opportunistic encryption, namely
the transfer of a http: request over a TLS connection.
Both cases are tricky on HTTP/1.x because the URI scheme is not transported in requests
(commonly. the spec wo
There is the reverse situation which is called opportunistic encryption, namely
the transfer of a http: request over a TLS connection.
Both cases are tricky on HTTP/1.x because the URI scheme is not transported in
requests (commonly. the spec would allow it but no one does it, so no one is
prep
