Mailing-List: contact users-help@httpd.apache.org; run by ezmlm
Precedence: bulk
Reply-To: users@httpd.apache.org
Received-SPF: pass (asf.osuosl.org: domain of krist.vanbesien@gmail.com
 designates 64.233.184.201 as permitted sender)
DomainKey-Signature: a=rsa-sha1; q=dns; c=nofws;
        s=beta; d=gmail.com;
        h=received:message-id:date:from:to:subject:in-reply-to:mime-version:content-type:content-transfer-encoding:content-disposition:references;
        b=sG7O0bnl+4Ga+0yeF15kv5AEm+DSbVNs5Kp8jk+Nay8nwj45b97WVlP5M4cwzKnNL7J9VqtojfaAPY26SN6TxFBm8QIdb5b7fjW5JFW0XRrEOThujlCaBWSffywU2Fra2ka6N8/ggXsjgsmX5iNSEZdHCYxXnxUTZhgxIJOj+oQ=
Message-ID: <6ed6382b0508040221236aaa33@mail.gmail.com>
Date: Thu, 4 Aug 2005 11:21:48 +0200
From: Krist van Besien <krist.vanbesien@gmail.com>
To: users@httpd.apache.org
In-Reply-To: <8C29B2F93BAE9047A906EF6D6F9C5D435ED4ED@exchange2k301.gaia.fr>
Mime-Version: 1.0
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: quoted-printable
Content-Disposition: inline
References: <8C29B2F93BAE9047A906EF6D6F9C5D435ED4ED@exchange2k301.gaia.fr>
Subject: Re: [users@httpd] Rewrite and https

On 8/4/05, Axel-St=E9phane  SMORGRAV
<Axel-Stephane.SMORGRAV@europe.adp.com> wrote:
> One thought at first: Couldn't your Weblogic server return a relative URL=
 rather than an absolute one, i.e. a URL not containing protocol and server=
 address ? Then this problem would not occur at all...


The problem is not only returning proper URLs but telling the weblogic
server that a request came in over https.

> OK. You probably have one virtual host handling the SSL traffic, the one =
with "SSLEngine On", right? You know that all requests handled by that virt=
ual host is HTTPS, right? So you do not need the condition (RewriteCond). W=
hy don't you just do either
>=20
> Header set protocol https
>=20
> or, if you absolutely want to use rewrite rules
>=20
> RewriteRule ^(/[Pp]ortal.*)     $1?protocol=3Dhttps       [QSA]
>=20
> I think that you will have to use different Java methods to retrieve the =
header in the two above cases.

I am not the one that decides which java method will be used, and the
powers that do decide about this have allready decided that they whant
the argument "protocol=3Dhttps"  added... So I have no option but to add
it...

An extra problem I have is that I have about a hundred rewrite rules,
and the order they are porcessed in is important. I don't know how to
add a rule to the  SSL virtual host, and maintain the processing order
I want. And I also don't want to maintain two complete sets of
rules...

I have now found out why it wouldn't work though. This is a bug in the
mod_rewrite shipped with apache 2.0. It definitely exists in 2.0.50,
but has aparently been fixed now. I'll upgrade when possible. In the
mean time the folowing workaround worked for me:

 # If Portal is accessed over https add a query parameter so the portal kno=
ws.
        RewriteCond     %{LA-U:ENV:HTTPS}        on
        RewriteRule ^/([Pp]ortal.*)     $1?protocol=3Dhttps       [QSA]

Krist


--=20
krist.vanbesien@gmail.com
Solothurn, Switzerland

---------------------------------------------------------------------
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