Am 2016-07-27 um 14:13 schrieb Nick Kew:
On Wed, 27 Jul 2016 14:01:09 +0200
Matthias Leopold <matth...@leopold.priv.at> wrote:
Check what headers are actually being exchanged between the
proxy and backend (and from the Client). The keepalive
timeouts are only relevant if all parties agree to them.
ProxyPass https://xxx ttl=20
Https? Do you get the same with plain HTTP?
Also, mod_proxy gets very verbose if you turn loglevel
up to Debug. Worth a try if it's not one of those problems
you solved one minute after posting!
i wish i solved this one minute after posting...
in the meantime i learned i can "solve" this with "SetEnv
proxy-initial-not-pooled 1", but this seems as brute-force as
"disablereuse=on" to me
i also get the error when backend is plain HTTP
when i turn on debug i get
mod_proxy_http.c(1499): [client x.x.x.x] proxy: NOT Closing connection
to client although reading from backend server foo failed.
in between
(70014)End of file found: proxy: error reading status line from remote
server
and
proxy: Error reading from remote server returned by xxx
does this give any clue?
i didn't look into packets yet as this server is rather busy
thanks
matthias
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscr...@httpd.apache.org
For additional commands, e-mail: users-h...@httpd.apache.org
