Justin Pasher wrote:
If you have more (sub)domains that point to the same virtualhost, then
you won't be able to use the above directive as-is, since it's
designed to funnel ALL requests through www.csulb.edu. It's mainly
designed for sites that have a handful of alias domains, but only one
Mike Soultanian wrote:
Justin Pasher wrote:
Ahhh... Now it should actually be possible. If possible, I would
(personally) try to push all traffic to www.csulb.edu whenever they
try to pull csulb.edu. Whether or not this is possible in your
situation, I do not know. Something like this in the V
Justin Pasher wrote:
Ahhh... Now it should actually be possible. If possible, I would
(personally) try to push all traffic to www.csulb.edu whenever they
try to pull csulb.edu. Whether or not this is possible in your
situation, I do not know. Something like this in the VirtualHost
config wou
Mike Soultanian wrote:
Justin Pasher wrote:
Actually, ignore everything I just said. All this time I thought that
was what apache was doing, but it's actually occurring after the
mismatched server name warning is presented. The rewrite rule will
still catch the request and redirect them to
Justin Pasher wrote:
Actually, ignore everything I just said. All this time I thought that
was what apache was doing, but it's actually occurring after the
mismatched server name warning is presented. The rewrite rule will
still catch the request and redirect them to https://www.csulb.edu,
Justin Pasher wrote:
Mike Soultanian wrote:
Justin Pasher wrote:
You can simplify this a bit by saying "redirect anything that is not
going to www.csulb.edu". However, you'll have to put the rewrite
directives inside the configuration for the SSL
version of the site, as the .htaccess file
On Mon, 29 Sep 2008 16:40:49 -0500, "Justin Pasher"
<[EMAIL PROTECTED]> said:
>
> If you do it within the apache config, the server will send the 302
> redirect header before trying to exchange any SSL key related
> information. Once they have been kicked over to
> https://www.csulb.edu/, the norm
Mike Soultanian wrote:
Justin Pasher wrote:
You can simplify this a bit by saying "redirect anything that is not
going to www.csulb.edu". However, you'll have to put the rewrite
directives inside the configuration for the SSL version
of the site, as the .htaccess file is run after a connect
Justin Pasher wrote:
You can simplify this a bit by saying "redirect anything that is not
going to www.csulb.edu". However, you'll have to put the rewrite
directives inside the configuration for the SSL version
of the site, as the .htaccess file is run after a connection is
established wi
Mike Soultanian wrote:
Our campus has an SSL certificate for www.csulb.edu. If you go to
https://www.csulb.edu everything works peachy.
Now, if you go to https://csulb.edu, you get an error. I talked to
our server admin and he said it's because our certificate is
registered to www.csulb.edu
Eric Covener wrote:
On Mon, Sep 29, 2008 at 4:25 PM, Mike Soultanian <[EMAIL PROTECTED]> wrote:
So, is it possible to set up a rewrite condition such that when someone
tries to navigate to https://csulb.edu, it will automatically redirect the
user to https://www.csulb.edu and avoid the certif
On Mon, Sep 29, 2008 at 4:25 PM, Mike Soultanian <[EMAIL PROTECTED]> wrote:
> Our campus has an SSL certificate for www.csulb.edu. If you go to
> https://www.csulb.edu everything works peachy.
>
> Now, if you go to https://csulb.edu, you get an error. I talked to our
> server admin and he said it
Our campus has an SSL certificate for www.csulb.edu. If you go to
https://www.csulb.edu everything works peachy.
Now, if you go to https://csulb.edu, you get an error. I talked to our
server admin and he said it's because our certificate is registered to
www.csulb.edu and not csulb.edu. He
13 matches
Mail list logo
