Return-Path: X-Original-To: apmail-httpd-users-archive@www.apache.org Delivered-To: apmail-httpd-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 63B63102A1 for ; Thu, 11 Jul 2013 14:42:13 +0000 (UTC) Received: (qmail 39340 invoked by uid 500); 11 Jul 2013 14:42:09 -0000 Delivered-To: apmail-httpd-users-archive@httpd.apache.org Received: (qmail 39237 invoked by uid 500); 11 Jul 2013 14:42:04 -0000 Mailing-List: contact users-help@httpd.apache.org; run by ezmlm Precedence: bulk Reply-To: users@httpd.apache.org list-help: list-unsubscribe: List-Post: List-Id: Delivered-To: mailing list users@httpd.apache.org Received: (qmail 39227 invoked by uid 99); 11 Jul 2013 14:42:03 -0000 Received: from nike.apache.org (HELO nike.apache.org) (192.87.106.230) by apache.org (qpsmtpd/0.29) with ESMTP; Thu, 11 Jul 2013 14:42:03 +0000 X-ASF-Spam-Status: No, hits=-0.0 required=5.0 tests=SPF_PASS X-Spam-Check-By: apache.org Received-SPF: pass (nike.apache.org: local policy) Received: from [209.183.20.202] (HELO mail.univeris.com) (209.183.20.202) by apache.org (qpsmtpd/0.29) with ESMTP; Thu, 11 Jul 2013 14:41:57 +0000 Received: from exch2007.univeris.com ([192.168.1.188]) by exch2007.univeris.com ([192.168.1.188]) with mapi; Thu, 11 Jul 2013 10:41:36 -0400 From: Stuart Irving To: "users@httpd.apache.org" Date: Thu, 11 Jul 2013 10:41:35 -0400 Thread-Topic: Can't get redirect or redirectmatch working in Windows Apache 2.2 but ok on Linux Thread-Index: Ac5+RL34UA3y+4zZR5CvcX5yp7RqmQ== Message-ID: Accept-Language: en-US Content-Language: en-US X-MS-Has-Attach: X-MS-TNEF-Correlator: acceptlanguage: en-US Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: quoted-printable MIME-Version: 1.0 X-Virus-Checked: Checked by ClamAV on apache.org Subject: [users@httpd] Can't get redirect or redirectmatch working in Windows Apache 2.2 but ok on Linux I am stuck on what is a very simple configuration that we have been using o= n Linux but it doesn't appear to trigger on windows. Below is what we have= in our conf file: ServerName xxxx.yyyy.ca Redirect / https://xxxx.yyyy.ca RedirectMatch (.*) https://xxxx.yyyy.ca$1 Note: I have tried various forms but my concern right now is not getting th= e url correct but just getting something in the browser: RedirectMatch ^/(.*) https://xxxx.yyyy.ca$1 RedirectMatch ^/(.*)$ https://xxxx.yyyy.ca$1 RedirectMatch ^/(.*)$ https://xxxx.yyyy.ca RedirectMatch ^/(.*)$ adsjfaksjfa I know it is hitting this section as the first Redirect works fine (and is = the only one in the entire configuration) but the RedirectMatch never appea= rs to trigger. I don't want to use alias or rewrites as I want the user to= see the change in their browser. The purpose is to transition this serve= r from 80 to 443 but we need to stage customers and not have them all of a = sudden find they can't access. What is unusual is even if I do Redirect /testme https://xxxx.yyyy.ca this = also doesn't trigger which is very strange. It almost appears that Apache = recognizes there is path information but not processing it correctly. This is the exact same syntax we use with httpd on Linux and it works fine.= We don't have any htaccess files anywhere so the only thing I can think of= is that there either is a bug in Windows or some very simple stupid flag o= r parameter I missed that windows needs. If anyone out there can point me in the right direction it would be greatly= appreciated. Univeris is a proud sponsor and participant of the 2013 IFIC Annual Golf Cl= assic on July 10th at Angus Glen Golf Club. We look forward to seeing you t= here and sharing a round of golf with friends, colleagues and clients! --- This e-mail message (including attachments, if any) is intended for the use= of the individual or entity to which it is addressed and may contain infor= mation that is privileged, proprietary, confidential and exempt from disclo= sure. If you are not the intended recipient, you are notified that any diss= emination, distribution or copying of this communication is strictly prohib= ited. If you have received this communication in error, please notify the = sender and erase this e-mail message immediately. Le pr?sent courrier ?lectronique (ainsi que les pi?ces qui y sont annex?es,= le cas ?ch?ant) s'adresse au destinataire indiqu? et peut contenir des ren= seignements privil?gi?s, confidentiels et/ou dispens?s de divulgation. Si = vous n'?tes pas le destinataire de ce document, nous vous signalons qu'il e= st strictement interdit de le diffuser, de le distribuer ou de le reproduir= e. Si ce message vous a ?t? transmis par erreur, veuillez en aviser l'exp?= diteur et le supprimer sans d?lai. --------------------------------------------------------------------- To unsubscribe, e-mail: users-unsubscribe@httpd.apache.org For additional commands, e-mail: users-help@httpd.apache.org