Return-Path: X-Original-To: archive-asf-public-internal@cust-asf2.ponee.io Delivered-To: archive-asf-public-internal@cust-asf2.ponee.io Received: from cust-asf.ponee.io (cust-asf.ponee.io [163.172.22.183]) by cust-asf2.ponee.io (Postfix) with ESMTP id 08CB1200BC1 for ; Wed, 16 Nov 2016 09:18:38 +0100 (CET) Received: by cust-asf.ponee.io (Postfix) id 05BCF160B08; Wed, 16 Nov 2016 08:18:38 +0000 (UTC) Delivered-To: archive-asf-public@cust-asf.ponee.io Received: from mail.apache.org (hermes.apache.org [140.211.11.3]) by cust-asf.ponee.io (Postfix) with SMTP id 2A702160B03 for ; Wed, 16 Nov 2016 09:18:37 +0100 (CET) Received: (qmail 87661 invoked by uid 500); 16 Nov 2016 08:18:36 -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 87646 invoked by uid 99); 16 Nov 2016 08:18:36 -0000 Received: from pnap-us-west-generic-nat.apache.org (HELO spamd3-us-west.apache.org) (209.188.14.142) by apache.org (qpsmtpd/0.29) with ESMTP; Wed, 16 Nov 2016 08:18:36 +0000 Received: from localhost (localhost [127.0.0.1]) by spamd3-us-west.apache.org (ASF Mail Server at spamd3-us-west.apache.org) with ESMTP id 846EE1809D8 for ; Wed, 16 Nov 2016 08:18:35 +0000 (UTC) X-Virus-Scanned: Debian amavisd-new at spamd3-us-west.apache.org X-Spam-Flag: NO X-Spam-Score: 4.009 X-Spam-Level: **** X-Spam-Status: No, score=4.009 tagged_above=-999 required=6.31 tests=[HEADER_FROM_DIFFERENT_DOMAINS=0.001, HTML_MESSAGE=2, KAM_BADIPHTTP=2, RCVD_IN_MSPIKE_H2=-0.001, SPF_PASS=-0.001, T_MIME_MALF=0.01] autolearn=disabled Received: from mx1-lw-eu.apache.org ([10.40.0.8]) by localhost (spamd3-us-west.apache.org [10.40.0.10]) (amavisd-new, port 10024) with ESMTP id lJyDU4cbbIO6 for ; Wed, 16 Nov 2016 08:18:34 +0000 (UTC) Received: from mail-pg0-f47.google.com (mail-pg0-f47.google.com [74.125.83.47]) by mx1-lw-eu.apache.org (ASF Mail Server at mx1-lw-eu.apache.org) with ESMTPS id E84E95F202 for ; Wed, 16 Nov 2016 08:18:33 +0000 (UTC) Received: by mail-pg0-f47.google.com with SMTP id x23so73982822pgx.1 for ; Wed, 16 Nov 2016 00:18:33 -0800 (PST) X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20130820; h=x-gm-message-state:from:mime-version:subject:date:references:to :in-reply-to:message-id; bh=JqLpixbO0JQg+Yii5XtebdSQo6DdPvZum115yiotbyA=; b=FZg3Pw14pmmiIm7X2YCaZjMkEfn9+xao0aAkx1tFGeFuVTCfauDsxuVyCeJo8h0Eyr LnxYW8fvWAU8W5p0d3xn2lkKoz9I4aYYkEJjDuQ97Kcj2YBTX7ndl24M6gL6BSWFlVbi ns3SyxeMI+RmfqkIDe6ntg2Nzk2DvQFhuEJRx3R1tJpBJ63Nwar7rzOqBnNSCT158VTH pK1tr8dOcNwm3D/SmqEfVz2oXsXerD86i0FR3S6WNe0lAm9HX1IAFv6aGNkB8gujXWEC y3bGv1cbaeltPTIIZO1UrrumdOw2lTQB2b4Pnr8RdN++ork/JiomA/q6LQgZoobhctvv Y3fw== X-Gm-Message-State: ABUngvc8G1BF0MHIU9kRTHeQMm1fjdhfM+567KxcFqnOH4YoZ0fk4at4DlaCWUXhfNTLsQ== X-Received: by 10.98.211.135 with SMTP id z7mr2806460pfk.109.1479284312450; Wed, 16 Nov 2016 00:18:32 -0800 (PST) Received: from t2001067c037001281d4f58c287a79eb7.v6.meeting.ietf.org ([2001:67c:370:128:1d4f:58c2:87a7:9eb7]) by smtp.gmail.com with ESMTPSA id i76sm50441214pfk.89.2016.11.16.00.18.30 for (version=TLS1_2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128/128); Wed, 16 Nov 2016 00:18:31 -0800 (PST) From: Bryan Call Content-Type: multipart/alternative; boundary="Apple-Mail=_3D3DFFBC-D023-4BE1-B082-37EC5F842032" Mime-Version: 1.0 (Mac OS X Mail 10.1 \(3251\)) Subject: Re: redirect Date: Wed, 16 Nov 2016 17:18:26 +0900 References: To: users@trafficserver.apache.org In-Reply-To: Message-Id: X-Mailer: Apple Mail (2.3251) archived-at: Wed, 16 Nov 2016 08:18:38 -0000 --Apple-Mail=_3D3DFFBC-D023-4BE1-B082-37EC5F842032 Content-Transfer-Encoding: quoted-printable Content-Type: text/plain; charset=utf-8 I ran a test myself and I don=E2=80=99t know of a way to make the = response cacheable. I assume you would like to set the Cache-Control = header to something like max-age=3D300. I will talk to a couple other = Committers tonight and see if they have any ideas. This is what I am seeing: [bcall@homer ~]$ curl -D - -H 'Host: www.google.com' = http://127.0.0.1:8080/ HTTP/1.1 301 Redirect Date: Wed, 16 Nov 2016 08:13:03 GMT Connection: keep-alive Server: ATS/7.1.0 Cache-Control: no-store Location: http://www.yahoo.com/ Content-Type: text/html Content-Language: en Content-Length: 303 -Bryan > On Nov 15, 2016, at 3:19 AM, $ubbu wrote: >=20 > Hi everyone >=20 > I am unable to cache the redirected urls, any way to cache the = redirected pages? >=20 > my rule is like this >=20 > redirect http://server1.example.com/ = http://serveraz.example.com/ >=20 > --=20 > Regards > Subrahmanya Prasad P --Apple-Mail=_3D3DFFBC-D023-4BE1-B082-37EC5F842032 Content-Transfer-Encoding: quoted-printable Content-Type: text/html; charset=utf-8 I ran a test myself and I don=E2=80=99t know of a way to make = the response cacheable.  I assume you would like to set the = Cache-Control header to something like max-age=3D300.  I will talk = to a couple other Committers tonight and see if they have any ideas.

This is what I am = seeing:
[bcall@homer ~]$ curl -D - = -H 'Host: www.google.com'= http://127.0.0.1:8080/
HTTP/1.1 301 = Redirect
Date: Wed, 16 Nov 2016 08:13:03 = GMT
Connection: keep-alive
Server: ATS/7.1.0
Cache-Control: no-store
Location: http://www.yahoo.com/
Content-Type: = text/html
Content-Language: en
Content-Length: 303

-Bryan




On Nov 15, 2016, at 3:19 AM, $ubbu <subbu448@gmail.com> = wrote:

Hi everyone

    I am unable to cache = the redirected urls, any way to cache the redirected pages?

my rule is like this

redirect http://server1.example.com/ http://serveraz.example.com/

--
Regards
Subrahmanya = Prasad P

= --Apple-Mail=_3D3DFFBC-D023-4BE1-B082-37EC5F842032--