Summary: Is it safe to set SSL host to “www.example.org/www.example.com”? It appears to exactly what I want, but it’s identified as “SSL host” not “SSL URL” and I’m a bit worried I’m relying on undefined behavior that may blow up in my face in a future WordPress or WordPress HTTPS update.
- http://www.example.com/ – Public face of site
- https://www.example.org/www.example.com/wp-admin – Administrative work is done here.
This is strange, but for reasons beyond my control I have SSL on http://www.example.org, but not http://www.example.com, but I really want http://www.example.com to be where most users see my site. I can’t put the WordPress install in the root of http://www.example.org, as http://www.example.org exists for entirely unrelated purposes.
WordPress HTTPS appears to do what I want. I have this working with a setup of:
- SSL Host: http://www.example.org/www.example.com
- Force SSL Administration: Yes
- Force SSL Exclusively: Yes
Is this safe? In particular, having put a (partial) URL in “SSL Host”, and I doing something undefined and stuff may break later?
(And if this is undefined, might I plead that support for this use case be added?)
Thanks for the plugin, it did get me going quickly on a new blog!
- The topic ‘Can "SSL Host" safely contain a path?’ is closed to new replies.