apache and mod_rewrite

[Joe Bielli]

I did a bit of searching and came up with a few rewrite options for you
to try...

#   Force clients from the Internet to use HTTPS
RewriteEngine        on
RewriteCond          %{HTTPS} !=on
RewriteRule          http://(.*) https://$1  [R]


Additionally, here is a page with several examples:
http://list.cobalt.com/pipermail/cobalt-developers/2001-August/033368.ht
ml

Hope it's somewhat helpful...

Joe


-----Original Message-----
From: owner-nflug at nflug.org [mailto:owner-nflug at nflug.org] On Behalf Of
Darin Perusich
Sent: Monday, October 28, 2002 10:27 AM
To: nflug at nflug.org
Subject: Re: apache and mod_rewrite

the software is the steltor calendar server and webclient.

unfortunately the only thing that you can specify is the path to the 
logout html page, there is no option to specify an actual url. the 
webclient itself is a binary CGI so there will be no hacking at it.

i've tried making the referal page a quick little php page that 
redirects to another site but the error is happening before apache put's

the page to the browser. because of this the only way that i can see to 
resolve this problem it to either 1. have steltor fix the binary (i've 
already contacted support), or 2. use mod_rewrite to rewrite the url.

Mark Musone wrote:
> It seems like you might be trying to solve the wrong problem...i'd
focus
> on solving the
> Problem of the invalid redirect, not solving the symptom of rewritting
> invalid URL's..
> 
> What software are you using? Cant you just change the logout url in
the
> code??
> 
> -Mark
> 
> 
> -----Original Message-----
> From: owner-nflug at nflug.org [mailto:owner-nflug at nflug.org] On Behalf
Of
> Darin Perusich
> Sent: Monday, October 28, 2002 9:07 AM
> To: nflug at nflug.org
> Subject: apache and mod_rewrite
> 
> 
> hello,
> 
> i'm trying to write a mod_rewrite rule to fix problem that i'm running

> into with an app on an ssl site. this app, a web calendar client is 
> working fine under ssl, when you logout it kick's you out to a user 
> defined page. during the logout process it tries to push you to a page

> with the following url: http://calendar.domain.com:443/logout.html,
this
> 
> produces a 400 Bad Request error from apache. the entire error is:
> 
> Bad Request
> Your browser sent a request that this server could not understand.
> 
> Reason: You're speaking plain HTTP to an SSL-enabled server port.
> Instead use the HTTPS scheme to access this URL, please.
> Hint: https://calendar.cognigencorp.com:443/
> 
> the rule i'm trying to write should take http://%{SERVER_NAME}:443 and

> write to https://%{SERVER_NAME}:443, so far i'm not having any luck.
> 
> anyone have experience writting these rules?
> 


-- 
Darin Perusich
Unix Systems Administrator
Cognigen Corp.
darinper at cognigencorp.com