3 messages in ru.sysoev.nginxRe: "add_header X-Upstream-Response-T...
FromSent OnAttachments
Matt AlbrightOct 8, 2008 10:54 am 
Maxim DouninOct 8, 2008 11:51 am 
Matt AlbrightOct 8, 2008 12:13 pm 
Actions with this message:
Paste this link in email or IM:
Paste this link in email or IM:
Atom feed for this thread
Paste this URL into your reader:
Subject:Re: "add_header X-Upstream-Response-Time $upstream_response_time" not workingActions...
From:Maxim Dounin (mdou@mdounin.ru)
Date:Oct 8, 2008 11:51:12 am
List:ru.sysoev.nginx

Hello!

On Wed, Oct 08, 2008 at 05:55:16PM +0000, Matt Albright wrote:

I'm using nginx 0.5.35 (I know, we'll upgrade here soon) and have $upstream_response_time in the access log, and it works great.

To track down a problem, I wanted to add a header to nginx's response that shows the response time of the upstream server, so I tried:

add_header X-Upstream-Response-Time $upstream_response_time

Which seems like it would work, based on the docs for add_header, but I get:

X-Upstream-Response-Time: 1223488205.821

Which looks like a unix time to me, which isn't very useful.

Yep. Since header is sent before we got whole response from upstream - we have no upstream end time at this point.

Is there any way to get what I want? I tried putting the add_header in http, server, and location blocks, but all of them gave me a unix time.

Currently no, only logging will work.

Probably it's a good idea to introduce another variable that will be available as soon as we got response header from upstream.