Apache 1.3 no ssl for al single script

 > Remove the enforcment of https for everything, use a rewrite rule
 > to use https instead of normal http for everything but that script.

I removed the redirect rule and added this rewrite rule:

RewtiteEngine on
RewriteCond %{SERVER_PORT} !443$
RewriteRule ^/(.*)$ <a style='text-decoration: underline;' href="https://my.domain.net/$1" target="_blank">https://my.domain.net/$1</a> [R,L]

This rule seems to force the usage of https instead of http.

But how can I add the exception for my script? Everything I
tried did not work properly.

Is there any better documentation available than the examples
in the apache manual?

Regards
Jens Meier<!-- ~MESSAGE_AFTER~ -->
 >> Stay informed about: Apache 1.3 no ssl for al single script 

"Jens Meier" <jens_meier12.DeleteThis@yahoo.de> schreef in bericht
news:cp26eg$keu$04$1@news.t-online.com...
  > > Remove the enforcment of https for everything, use a rewrite rule
  > > to use https instead of normal http for everything but that script.
 > I removed the redirect rule and added this rewrite rule:
 > RewtiteEngine on
 > RewriteCond %{SERVER_PORT} !443$
 > RewriteRule ^/(.*)$ <a style='text-decoration: underline;' href="https://my.domain.net/$1" target="_blank">https://my.domain.net/$1</a> [R,L]
 >
 > This rule seems to force the usage of https instead of http.
 >
 > But how can I add the exception for my script? Everything I
 > tried did not work properly.
Add in between the current rule and condition
RewriteCond %{REQUEST_URI} !^/pathand/script2skip.cgi$

Be aware the links to this script _must_ include protocol, otherwise a
browser will use the protocol of its referer: https!
(You might also add a rewrite and set of conditions to map such a request
back to the plain http site)
Mixing multiple protocols on a single page may cause a brower to carp about
entering and leaving a protected area.

HansH<!-- ~MESSAGE_AFTER~ -->
 >> Stay informed about: Apache 1.3 no ssl for al single script 

Hello,

 > Add in between the current rule and condition
 > RewriteCond %{REQUEST_URI} !^/pathand/script2skip.cgi$

This works! Thank you very much.
Meanwhile I also found a better mod_rewrite documentation at
<a style='text-decoration: underline;' href="http://httpd.apache.org/docs/mod/mod_rewrite.html" target="_blank">http://httpd.apache.org/docs/mod/mod_rewrite.html</a>

But I still have a question: Now there are 2 RewriteCond
statements in my httpd.conf. According to the mod_rewrite
documentation the RewriteRule will only be applied, if both
RewriteConds match. Did I unterstand this correctly?
 > Be aware the links to this script _must_ include protocol, otherwise a
 > browser will use the protocol of its referer: https!
 > (You might also add a rewrite and set of conditions to map such a
request
 > back to the plain http site)
 > Mixing multiple protocols on a single page may cause a brower to carp
about
 > entering and leaving a protected area.

This won´t be a problem in my case as the script is only
needed by a client program (which doen´t work with https).
 > Be aware the links to this script _must_ include protocol, otherwise a
 > browser will use the protocol of its referer: https!
 > (You might also add a rewrite and set of conditions to map such a
request
 > back to the plain http site)
 > Mixing multiple protocols on a single page may cause a brower to carp
about
 > entering and leaving a protected area.<!-- ~MESSAGE_AFTER~ -->
 >> Stay informed about: Apache 1.3 no ssl for al single script 

Hello,

my last message was posted accidentally before
I had formated it correctly so apologise the bad
quotation in the last passage.

Thank you for your help again!
Jens Meier
 >> Stay informed about: Apache 1.3 no ssl for al single script 

"Jens Meier" <jens_meier12.DeleteThis@yahoo.de> schreef in bericht
news:cp484k$dk9$02$1@news.t-online.com...
  > > Add in between the current rule and condition
  > > RewriteCond %{REQUEST_URI} !^/pathand/script2skip.cgi$
 >
 > This works! Thank you very much.
 > Meanwhile I also found a better mod_rewrite documentation at
<font color=purple> > <a style='text-decoration: underline;' href="http://httpd.apache.org/docs/mod/mod_rewrite.html</font" target="_blank">http://httpd.apache.org/docs/mod/mod_rewrite.html</font</a>>
 >
 > But I still have a question: Now there are 2 RewriteCond
 > statements in my httpd.conf. According to the mod_rewrite
 > documentation the RewriteRule will only be applied, if both
 > RewriteConds match. Did I unterstand this correctly?
Default behaviour is indeed AND as documented at
<a style='text-decoration: underline;' href="http://httpd.apache.org/docs/mod/mod_rewrite.html#RewriteCond," target="_blank">http://httpd.apache.org/docs/mod/mod_rewrite.html#RewriteCond,</a> though the OR
flag allowes one to OR conditions.
However, if some simple conditions are applied to the same request property,
RewriteCond %{REMOTE_HOST} ^host1\.* [OR]
RewriteCond %{REMOTE_HOST} ^host2\.* [OR]
RewriteCond %{REMOTE_HOST} ^host3\.*
a regular expression should do a better job
RewriteCond %{REMOTE_HOST} ^(host1|host2|host3)\.*

The result of the following
RewriteCond %{REMOTE_HOST} ^host1\.* [OR]
RewriteCond %{REMOTE_HOST} ^host2\.* [OR]
RewriteCond %{REMOTE_HOST} ^host3\.*
RewriteCond %{SERVER_PORT} !443$
cannt be predicted by documentation -boolean math may execute AND before
OR-, however
RewriteCond %{SERVER_PORT} !443$
RewriteCond %{REMOTE_HOST} ^(host1|host2|host3)\.*
is fully predictable.


Your current conditions do not redirect requests at port 4443 ...
.... using "RewriteCond %{SERVER_PORT} !^443$" is more accurate.

HansH<!-- ~MESSAGE_AFTER~ -->
 >> Stay informed about: Apache 1.3 no ssl for al single script 

Hello,

 > Default behaviour is indeed AND as documented at
<font color=purple> > <a style='text-decoration: underline;' href="http://httpd.apache.org/docs/mod/mod_rewrite.html#RewriteCond,</font" target="_blank">http://httpd.apache.org/docs/mod/mod_rewrite.html#RewriteCond,</font</a>>

That's what I wanted to make sure.

 > Your current conditions do not redirect requests at port 4443 ...
 > ... using "RewriteCond %{SERVER_PORT} !^443$" is more accurate.

You are right . I must have overlooked the missing ^. But my apache
only listens to port 443 (and 80 of course) anyway.


Regards
Jens Meier<!-- ~MESSAGE_AFTER~ -->
 >> Stay informed about: Apache 1.3 no ssl for al single script