On 4/17/2014 3:46 PM, Yehuda Katz wrote:
On Thu, Apr 17, 2014 at 3:12 PM, Mark London mailto:m...@psfc.mit.edu>>wrote:
So I've been trying to find a configuration that redirects
HTTPS://XXX.COMto HTTPS://WWW.XXX.COM. Unfortunately,
every configuration that I've tried, doesn't work. Al
Do the users actually connect to "https://xxx.com"; ? Or do they go just to
"xxx.com" in their browser and then a load-balancer/SSL-accellerator
somewhere along the way bumps them to https?
If something was bumping them to https then it would be easiest to just
change that 'bumping' to go from "h
On Thu, Apr 17, 2014 at 3:12 PM, Mark London wrote:
> So I've been trying to find a configuration that redirects HTTPS://XXX.COMto
> HTTPS://WWW.XXX.COM. Unfortunately, every configuration that I've tried,
> doesn't work. All of the rewrite and redirect rules, are applied after the
> browser ch
Hi - I inherited a web server from another site. I requested a
wildcard certificate for that server. What I failed to realize, was
that a wildcard certificate only covers *.XXX.COM. It won't cover plain
XXX.COM. And unfortunately, people mainly connect to the site, using
XXX.COM Thus,
