On 4/5/06, Mike McMullen <mlm@xxxxxxxxxxxxxxxxxx> wrote:
>
> Hi All,
>
> Let me start off by stating I are ignernt of rewriting rules. In our .htaccess
> files on our server I have the following magic that forces connections for
> user-based directories to an SSL connection:
>
> RewriteEngine on
>
> RewriteCond %{SERVER_PORT} ^80$
> RewriteCond %{PATH_INFO} ^$
> RewriteRule ^(.*) https://www.mydomain.com/~myuserid/ [L]
>
>
> RewriteCond %{SERVER_PORT} ^80$
> RewriteRule ^(.*) https://www.mydomain.com/~myuserid/$1
>
>
> This magic was given to me awhile ago.
>
> The new server I am putting in has multiple network cards in it. I would
> like to if necessary force the incoming connection to use SSL but
> stay on the same network path that the connection was initiated
> with. One advantage is this keeps from going out of the internal
> network, through a router and into the nic defined as the internet
> facing IP.
>
> Can someone show me what I need to change in the above?
Perhaps I don't understand what you want, but this doesn't make much
sense to me. If I had to guess at what you are saying, then perhaps
you have some people accessing the site from an intranet and others
accessing it from the Internet. If they are using different
hostnames, then you can replace www.mydomain.com with %{HTTP_HOST} to
make sure they stay with the same hostname.
Otherwise, apache has no control whatsoever over the network path
between the client and the server.
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@xxxxxxxxxxxxxxxx
" from the digest: users-digest-unsubscribe@xxxxxxxxxxxxxxxx
For additional commands, e-mail: users-help@xxxxxxxxxxxxxxxx
|