Oops, my mistake. I was looking at the wrong logs. The upstream connect and
response times are indeed reported.
Now that I have analyzed the timing logs, I see that there is a networking
issue between the proxy and the origin.
Roger
> On Jan 23, 2019, at 10:00 AM, Maxim Dounin wrote:
>
> He
Hello!
On Wed, Jan 23, 2019 at 09:03:33AM -0800, Roger Fischer wrote:
> I am using the community version of NGINX, where these variables
> are not available (I was quite disappointed by that).
Again: these variables are available in all known variants of
nginx. In particular, the $upstream_re
I am using the community version of NGINX, where these variables are not
available (I was quite disappointed by that).
Roger
> On Jan 23, 2019, at 5:23 AM, Maxim Dounin wrote:
>
> Hello!
>
> On Tue, Jan 22, 2019 at 04:48:23PM -0800, Roger Fischer wrote:
>
>> I have noticed that the response
Hello!
On Tue, Jan 22, 2019 at 04:48:23PM -0800, Roger Fischer wrote:
> I have noticed that the response to OPTIONS requests via a
> reverse proxy cache are quite slow. The browser reports 600 ms
> or more of idle time until NGINX provides the response. I am
> using the community edition of NG
Hello,
I have noticed that the response to OPTIONS requests via a reverse proxy cache
are quite slow. The browser reports 600 ms or more of idle time until NGINX
provides the response. I am using the community edition of NGINX, so I don’t
have any timing for the upstream request.
As I understa
