On 9/16/05, Carl Johnstone <[EMAIL PROTECTED]> wrote:
Can add my voice to the "BigIP should do this" school of thought. If it'seffectively converting HTTPS into HTTP requests for you, then I would expectit should be able to rewrite redirects automatically for you too. Same way
that apache does it i
On 9/16/05, Jeff <[EMAIL PROTECTED]> wrote:
In your BigIPs Apache httpd.conf you might try:# bounce to https only) ServerName www.mywebsite.com Redirectpermanent /
https://www.mywebsite.com/Which tells your client browsers to use HTTPS for all requests for therelevant website.
Unfortunate
On 9/16/05, Torsten Foertsch <[EMAIL PROTECTED]> wrote:
Maybe in it is sufficient to set $r->subprocess_env(HTTPS=>'on') in aPostReadRequest handler. Maybe even PerlSetEnv outside any or might help. This will also set environment variables very early.
$ENV{HTTPS} is not good.
Ah, I'd neglected to
Damyan Ivanov wrote:
Wouldn't it be better to parse responses on BigIPs and replace 'http'with 'https' if redirect is detected? I have no idea how to do this, though.
The BigIP has some TCL functions available during the response, but I'm
assuming that any regexing I do there would be not enough,
Can add my voice to the "BigIP should do this" school of thought. If it's
effectively converting HTTPS into HTTP requests for you, then I would expect
it should be able to rewrite redirects automatically for you too. Same way
that apache does it in mod_proxy.
However can I also point out tha
On Friday 16 September 2005 02:05, Mark Moseley wrote:
> Greetings. I've been scouring the list and the net for a solution for this
> but my apologies in advance if I didn't get the search terms right and
> missed a RTFM answer.
>
> I work for a web hosting company and we recently purchased a pair
Wouldn't it be better to parse responses on BigIPs and replace 'http'
with 'https' if redirect is detected? I have no idea how to do this, though.
In your BigIPs Apache httpd.conf you might try:
# bounce to https only)
ServerName www.mywebsite.com
Redirectpermanent / https://www.myw
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Mark Moseley wrote:
> Howdy. Actually, I don't need any actual SSL functionality. All I need
> to do is to trick everything from the transhandler phase downwards that
> the URL's scheme is 'https' so that redirects have https://, not
> http://, since a
Howdy. Actually, I don't need any actual SSL functionality. All I need
to do is to trick everything from the transhandler phase downwards that
the URL's scheme is 'https' so that redirects have https://, not
http://, since anyone doing a mod_rewrite or scripted redirect whilst
in SSL would get shun
Hi Mark,
From my limited knowledge, SSL handshake is processed prior doing the HTTP
request-response. Therefore, when apache or mod_perl accepts HTTPS requests,
it can't redirect it over HTTPS unless you create another HTTPS request with
LWP or WWW::Mechanize, for example.
But if you want to
10 matches
Mail list logo
