upstream sent no valid HTTP/1.0 header while reading response header from upstream,

2021-01-26 Thread sanflores
I'm using tomcat as a backend (using websocket), and is hostead on AWS behind a balancer. After a some time (acording to timeouts) I'm starting to get the error that the upstream sent no valid HTTP/1.0, but what is strange, is that I'm only using HTTP/1.1, this is my configuration: #

Re: proxy_cache_valid depending on $host

2021-01-26 Thread Phil Endecott
Maxim Dounin wrote: On Mon, Jan 25, 2021 at 04:26:49PM +, Phil Endecott wrote: Is there some work-around to have different cache validity times for different hosts, in a caching proxy? Using different server{} blocks with different server_name's is the way to go, see http://nginx.org/r/se