On 05/21/2010 02:02 PM, Ski Dawg wrote:
> Thanks to everyone else for the replies on this topic. I scanned
> through all of the logs for the last month, and this has only come up
> twice in that entire time, and I believe they change that I made to
> redirect them to http://www.domainname.com (inst
On 22 May 2010 00:00, Barry Brimer wrote:
>> On 21 May 2010 22:04, Ski Dawg wrote:
>>>
>>> On Wed, May 19, 2010 at 7:45 PM, Barry Brimer wrote:
As for the redirection, I would handle it with mod_rewrite as follows:
ServerName domain.tld
RewriteCond %{HTTP_HOST} !
On 21 May 2010 22:04, Ski Dawg wrote:
On Wed, May 19, 2010 at 7:45 PM, Barry Brimer wrote:
As for the redirection, I would handle it with mod_rewrite as follows:
ServerName domain.tld
RewriteCond %{HTTP_HOST} !^www\.domain\.tld$ [NC]
RewriteCond %{HTTP_HOST} !^$
RewriteRule ^/(.*)
On 21 May 2010 22:04, Ski Dawg wrote:
> On Wed, May 19, 2010 at 7:45 PM, Barry Brimer wrote:
>> As for the redirection, I would handle it with mod_rewrite as follows:
>>
>>
>> ServerName domain.tld
>> RewriteCond %{HTTP_HOST} !^www\.domain\.tld$ [NC]
>> RewriteCond %{HTTP_HOST} !^$
>> Rewrit
On Wed, May 19, 2010 at 7:45 PM, Barry Brimer wrote:
> As for the redirection, I would handle it with mod_rewrite as follows:
>
>
> ServerName domain.tld
> RewriteCond %{HTTP_HOST} !^www\.domain\.tld$ [NC]
> RewriteCond %{HTTP_HOST} !^$
> RewriteRule ^/(.*) https://www.domain.tld/$1 [
On Thu, May 20, 2010 at 5:25 AM, Robert Heller wrote:
> Do you have logs / Google Analytics reports that show that visitors are
> actually landing on https://www.domainname.com (other than your
> testing)? If not, you can show this to management.
Thanks to everyone else for the replies on this t
At Wed, 19 May 2010 17:43:14 -0500 CentOS mailing list
wrote:
>
> On 5/19/2010 4:52 PM, Robert Heller wrote:
> >
> > Is there any *legitimate* reason why someone would want to *type*
> > https://domainname.com in the location/address bar? There really should
> > not be a reason to do that.
>
>
At Wed, 19 May 2010 16:36:00 -0600 CentOS mailing list
wrote:
>
> On Wed, May 19, 2010 at 3:52 PM, Robert Heller wrote:
> > Is there any *legitimate* reason why someone would want to *type*
> > https://domainname.com in the location/address bar? There really should
> > not be a reason to do th
put this into root of the domain into the .htaccess file
RewriteCond %{HTTP_HOST} !^www\. [NC]
RewriteCond %{REMOTE_HOST} !^.*YOURDOMAIN\.com [NC]
RewriteRule ^(.*)$ http://www.%{HTTP_HOST}/$1 [R=301,L]
Jobst
On Wed, May 19, 2010 at 02:08:59PM -0600, Ski Dawg (cen...@skidawg.org) wrote:
>
> I think that I am going to push at management that this is a non-issue
> and not worth wasting any more time and see what they might say.
I'd like to point out that the following sites don't work with
https://domain.tld/
amazon.com
usbank.com
redhat.com
etrade.com
They all present certs for w
On 05/19/2010 02:02 PM, Zack Colgan wrote:
> The problem you are running into is that SSL sessions are negotiated
> prior to the browser sending the virtual host name, so there is no
> opportunity to redirect the client to the www URL before it's too late.
> Aside from purchasing a second SSL cer
On Wed, May 19, 2010 at 4:43 PM, Les Mikesell wrote:
> On 5/19/2010 4:52 PM, Robert Heller wrote:
>>
>> Is there any *legitimate* reason why someone would want to *type*
>> https://domainname.com in the location/address bar? There really should
>> not be a reason to do that.
>
> How else would you
On 5/19/2010 4:52 PM, Robert Heller wrote:
>
> Is there any *legitimate* reason why someone would want to *type*
> https://domainname.com in the location/address bar? There really should
> not be a reason to do that.
How else would you get there the first time?
--
Les Mikesell
lesmikes...
On Wed, May 19, 2010 at 3:52 PM, Robert Heller wrote:
> Is there any *legitimate* reason why someone would want to *type*
> https://domainname.com in the location/address bar? There really should
> not be a reason to do that. If people are doing this, then that means
> there is some reason for it
At Wed, 19 May 2010 15:29:51 -0600 CentOS mailing list
wrote:
>
> On Wed, May 19, 2010 at 3:02 PM, Zack Colgan
> wrote:
> > On 05/19/2010 04:08 PM, Ski Dawg wrote:
> >> The problem I am running into is if they go to https://domainname.com
> >> (straight to the secure site), I am not able to fi
Ski Dawg wrote:
> On Wed, May 19, 2010 at 3:02 PM, Zack Colgan
> wrote:
>
>> On 05/19/2010 04:08 PM, Ski Dawg wrote:
>>
>>> The problem I am running into is if they go to https://domainname.com
>>> (straight to the secure site), I am not able to find a solution that
>>> will redirect them
At Wed, 19 May 2010 17:02:31 -0400 CentOS mailing list
wrote:
>
> On 05/19/2010 04:08 PM, Ski Dawg wrote:
> > The problem I am running into is if they go to https://domainname.com
> > (straight to the secure site), I am not able to find a solution that
> > will redirect them to https://www.doma
At Wed, 19 May 2010 15:21:06 -0600 CentOS mailing list
wrote:
>
> On Wed, May 19, 2010 at 2:33 PM, Robert Heller wrote:
> > At Wed, 19 May 2010 14:08:59 -0600 CentOS mailing list
> > wrote:
> >>
> >> Â Â ServerName domainname.com
> >> Â Â Redirect permanent / http://www.domainname.com/
On Wed, May 19, 2010 at 3:02 PM, Zack Colgan
wrote:
> On 05/19/2010 04:08 PM, Ski Dawg wrote:
>> The problem I am running into is if they go to https://domainname.com
>> (straight to the secure site), I am not able to find a solution that
>> will redirect them to https://www.domainname.com, so tha
On Wed, May 19, 2010 at 2:33 PM, Robert Heller wrote:
> At Wed, 19 May 2010 14:08:59 -0600 CentOS mailing list
> wrote:
>>
>> ServerName domainname.com
>> Redirect permanent / http://www.domainname.com/
>>
>
> You don't really need this -- you can just add the line below to your existi
On Wed, May 19, 2010 at 2:13 PM, Craig White wrote:
> On Wed, 2010-05-19 at 14:08 -0600, Ski Dawg wrote:
>> I found one site that said to make a change to the apache conf file,
>> which I have done. The change that I made is adding:
>>
>> ServerName domainname.com
>> Redirect permanent /
On 05/19/2010 04:08 PM, Ski Dawg wrote:
> The problem I am running into is if they go to https://domainname.com
> (straight to the secure site), I am not able to find a solution that
> will redirect them to https://www.domainname.com, so that the ssl
> certificate matches and they won't get the "Th
At Wed, 19 May 2010 14:08:59 -0600 CentOS mailing list
wrote:
>
> Hello everyone,
>
> Part of our website has secured access with an SSL certificate. The
> problem we are running into is that the certificate is for
> www.domainname.com, so when they go to domainname.com (without the
> www. in
On Wed, 2010-05-19 at 14:08 -0600, Ski Dawg wrote:
> Hello everyone,
>
> Part of our website has secured access with an SSL certificate. The
> problem we are running into is that the certificate is for
> www.domainname.com, so when they go to domainname.com (without the
> www. in front), the users
24 matches
Mail list logo
