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 2617811665 for ; Thu, 24 Apr 2014 06:23:04 +0000 (UTC) Received: (qmail 13416 invoked by uid 500); 24 Apr 2014 06:23:03 -0000 Delivered-To: apmail-trafficserver-users-archive@trafficserver.apache.org Received: (qmail 12955 invoked by uid 500); 24 Apr 2014 06:22:55 -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 12941 invoked by uid 99); 24 Apr 2014 06:22:54 -0000 Received: from athena.apache.org (HELO athena.apache.org) (140.211.11.136) by apache.org (qpsmtpd/0.29) with ESMTP; Thu, 24 Apr 2014 06:22:54 +0000 X-ASF-Spam-Status: No, hits=-0.0 required=5.0 tests=SPF_PASS X-Spam-Check-By: apache.org Received-SPF: pass (athena.apache.org: local policy includes SPF record at spf.trusted-forwarder.org) Received: from [209.20.83.52] (HELO gungnir.webthing.com) (209.20.83.52) by apache.org (qpsmtpd/0.29) with ESMTP; Thu, 24 Apr 2014 06:22:48 +0000 Received: from [192.168.0.5] (cpc14-newt30-2-0-cust22.newt.cable.virginm.net [92.232.45.23]) by gungnir.webthing.com (Postfix) with ESMTPSA id 66472128002 for ; Thu, 24 Apr 2014 06:22:27 +0000 (UTC) Message-ID: <1398320545.27535.2.camel@mimir.webthing.com> Subject: Re: Odd 302 behavior From: Nick Kew To: users@trafficserver.apache.org Date: Thu, 24 Apr 2014 07:22:25 +0100 In-Reply-To: References: Content-Type: text/plain; charset="UTF-8" X-Mailer: Evolution 3.4.4-3 Mime-Version: 1.0 Content-Transfer-Encoding: 7bit X-Virus-Checked: Checked by ClamAV on apache.org On Wed, 2014-04-23 at 22:28 -0400, Frank Smith wrote: > When I tail the extended2.log file during my reverse proxy request, I > see the GET to https://app.mydomain.com with a 302 status. Is that trafficserver's log? What does the backend get? And did matching slashes fix anything? -- Nick Kew