Return-Path: X-Original-To: apmail-trafficserver-users-archive@www.apache.org Delivered-To: apmail-trafficserver-users-archive@www.apache.org Received: from mail.apache.org (hermes.apache.org [140.211.11.3]) by minotaur.apache.org (Postfix) with SMTP id 9A39610226 for ; Sat, 23 Nov 2013 02:14:26 +0000 (UTC) Received: (qmail 42450 invoked by uid 500); 23 Nov 2013 02:14:26 -0000 Delivered-To: apmail-trafficserver-users-archive@trafficserver.apache.org Received: (qmail 42253 invoked by uid 500); 23 Nov 2013 02:14:26 -0000 Mailing-List: contact users-help@trafficserver.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Reply-To: users@trafficserver.apache.org Delivered-To: mailing list users@trafficserver.apache.org Received: (qmail 42245 invoked by uid 99); 23 Nov 2013 02:14:26 -0000 Received: from minotaur.apache.org (HELO minotaur.apache.org) (140.211.11.9) by apache.org (qpsmtpd/0.29) with ESMTP; Sat, 23 Nov 2013 02:14:26 +0000 Received: from localhost (HELO [10.0.0.11]) (127.0.0.1) (smtp-auth username jpeach, mechanism plain) by minotaur.apache.org (qpsmtpd/0.29) with ESMTP; Sat, 23 Nov 2013 02:14:25 +0000 Content-Type: text/plain; charset=iso-8859-1 Mime-Version: 1.0 (Mac OS X Mail 7.0 \(1812\)) Subject: Re: Adding headers to 304 Responses From: James Peach In-Reply-To: Date: Fri, 22 Nov 2013 18:14:23 -0800 Content-Transfer-Encoding: quoted-printable Message-Id: References: To: users@trafficserver.apache.org X-Mailer: Apple Mail (2.1812) On Nov 22, 2013, at 4:59 PM, Mark Moseley wrote: > On Fri, Nov 22, 2013 at 4:46 PM, Shu Kit Chan = wrote: > =46rom the header_rewrite plugin perspective,=20 > the 304 is coming straight out of ATS and not from origin server. = That's fine. > So all the plugin does is to look up "X-From-Apache" from this = particular HTTP response between ATS and the client. It can't find it. = So it cancelled the add-header operation for "X-ATS-1". > But the add-header operation for "X-ATS-2" is still getting done = without problem. >=20 >=20 >=20 > However the header that's not seen by the headers_rewrite module is = stored in the cached response. If I do a non-conditional, non-"Pragma: = no-cache" request, there's likewise no request to the origin server but = the header gets seen by the headers_module. >=20 > So I'm trying to figure out how to amend the list of headers ATS = should send back, in the event of a cache-fulfilled 304 request. It might help to trace the "header_rewrite" diagnostic tag with = proxy.config.diags.debug.tags. Can you also post your header_rewrite = config file ... I've found that the syntax can be unintuitive ... J=