On 12/14/06, Foster, Stephen (ASPIRE) <steve.foster@[...].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 bro
wser gets a URL sent back with a URI added including the original URL of http://www.domain.c
om , 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 an
d 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 develo
pers change it without me knowing. However if needs be then i can intercept "APPURI=http:" a
nd 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@[...].org
   "   from the digest: users-digest-unsubscribe@[...].org
For additional commands, e-mail: users-help@httpd.apache.org