log_format access '$remote_addr - $remote_user [$time_local] "$request"
$http_host $status $body_bytes_sent "$http_referer" "$http_x_forwarded_for"
"$upstream_addr" "$upstream_status" $upstream_cache_status
"$upstream_http_content_type" "$upstream_response_time" > $request_time
"$http_user_age
Maybe that "proxy_buffering on" badly interacts with websockets?
On Sun, Oct 11, 2015 at 2:42 PM, javdev wrote:
> Hello guys this is my first question here.
>
> I'm working on nginx almost 2 years, but in the laste days I have founded an
> error, very complicated to solve.
>
> I'm working on Amaz
Hello!
On Sun, Oct 11, 2015 at 05:42:37PM -0400, javdev wrote:
> Hello guys this is my first question here.
>
> I'm working on nginx almost 2 years, but in the laste days I have founded an
> error, very complicated to solve.
>
> I'm working on Amazon stack, with Elastic Load Balancer (Using TCP
Hello guys this is my first question here.
I'm working on nginx almost 2 years, but in the laste days I have founded an
error, very complicated to solve.
I'm working on Amazon stack, with Elastic Load Balancer (Using TCP (SSL)),
then the request is sent to Nginx (1.8.0), 2 EC2 Instances, each ins
