Mailing-List: contact users-help@httpd.apache.org; run by ezmlm
Precedence: bulk
Reply-To: users@httpd.apache.org
Received-SPF: pass (herse.apache.org: domain of jslive@gmail.com designates
 209.85.132.248 as permitted sender)
DomainKey-Signature: a=rsa-sha1; q=dns; c=nofws;
        s=beta; d=gmail.com;
        h=received:message-id:date:from:sender:to:subject:in-reply-to:mime-version:content-type:content-transfer-encoding:content-disposition:references:x-google-sender-auth;
        b=je+RNLULB+WX5/Fqft+zuVqjmJHmiXgsbCpHMqdAZkqPz03yY6XWuwjmN7khvM3UsfmIlPvQ9ZZG2S8v6zFPOAQrJqVV1m0R+4zBiaFjfGm4BQyIl03+9Nb5y4CAWjdpbNcC8GO/XiYx6ou5PdvR2cTZ/BU6d5A4ffydLtyt33M=
Message-ID: <e498c1660612140707i65b8086uf70eeeb46d74a0c9@mail.gmail.com>
Date: Thu, 14 Dec 2006 10:07:26 -0500
From: "Joshua Slive" <joshua@slive.ca>
Sender: jslive@gmail.com
To: users@httpd.apache.org
In-Reply-To: 
 <F0700F1A7864D44DAC1E349169176E63041E00B9@MISSHPEXVS03.hmrcmis.net>
MIME-Version: 1.0
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
Content-Disposition: inline
References: 
 <F0700F1A7864D44DAC1E349169176E63041E00B9@MISSHPEXVS03.hmrcmis.net>
Subject: Re: [users@httpd] re-writing URI's

On 12/14/06, Foster, Stephen (ASPIRE) <steve.foster@hmrcaspire.com> wrote:
> Hi there,
>
> i'm having a bit of trouble getting a rewrite rule for a URI to work.
> Basically i have the following scenario,
>
> The user enters http://www.domain.com and this gets intercepted by another API and the browser gets a URL sent back with a URI added including the original URL of http://www.domain.com , my re-writing rules then re-write the first part to secure, i.e https://www.domain.com but the URI stays non-secure ,e.g http://www.domain.com
>
> so the outcome to the browser is:
>
> https://www.domain.com/login?APPURI=http://www.domain.com/home
>
> What i need to do when i re-write the first part to secure is also to intercept the URI and re-write this to secure if it comes back as non-secure, so i need the URL being sent back to the browser to appear as follows:
> https://www.domain.com/login?APPURI=https://www.domain.com/home
>
> I know i can use the RewriteCond %{REQUEST_URI} context but need to be able to tell it to find "http:" and re-write this to "https:" wherever it appears in the URI in case the developers change it without me knowing. However if needs be then i can intercept "APPURI=http:" and rewrite this to "APPURI=https:"
>
> Does that make sense to anybody??

Sure, it should be a relatively straightforward regex with
substitution.  But I'm not going to try to guess at your entire
config.  Show us what you've got already and we can perhaps tell you
what to add.

Joshua.

---------------------------------------------------------------------
The official User-To-User support forum of the Apache HTTP Server Project.
See <URL:http://httpd.apache.org/userslist.html> for more info.
To unsubscribe, e-mail: users-unsubscribe@httpd.apache.org
   "   from the digest: users-digest-unsubscribe@httpd.apache.org
For additional commands, e-mail: users-help@httpd.apache.org