The thing is... I don't feel I should have to "force SSL" and = seems "Chrome" browser already does that as I have to use Safari to = access non SSL side!
With that being said... Google Chrome is forcing us to have a = Home pages in both SSL and non SSL sites!!!! I have 25 Domains woking = dynamically as the "same site"
http://auto-glass-xpress.com/ (SSL version) and
http://xpress.glass/ (non = SSL). If u load
auto-glass-xpress.com no SSL into Chrome it will = automatically switch the client into SSL!!! So I have no way of knowing = if client is port 80 or 443! AND if they are ALREADY on 443 on a form I = DON'T have to do a redirect! And I have more than 2 domain names per = group of sites!
Also had it out with Godaddy the other day! I buy cert for 5 = domains and only the first one in the group works with "www"
www.example.com and the = others don't!
Also, my sites were originally = designed to read the sub-domains dynamically so I could serve the right = category or area. ex:
na.usa.new_york.buffalo.example.com AND because a few are = selling "sub-domains" ex:
biz1.uk.com and
biz2.uk.com WE can NOT get multi-level wildcard SSL's and = single wild-cards are expensive!
It's less effort = typing "*" than "www' or the hundred other sub domains!
This is a my actual DNS = below and I use it for ALL my domain names! I think it's = engenius!
| Type | Name | Value | TTL | Actions |
|---|
| A | *<= /td> | 74= ..77.225.229 | 1 = Hour | Edit |
| A | *.= * | 74= ..77.225.229 | 1 = Hour | Edit |
| A | *.= *.* | 74= ..77.225.229 | 1 = Hour | Edit |
| A | *.= *.*.* | 74= ..77.225.229 | 1 = Hour | Edit |
| A | @<= /td> | 74= ..77.225.229 | 1 = Hour |