Secure URL and non standard HTTP/HTTPS ports
-
For various reasons you sometime have to use non standard HTTP and HTTPS ports.
For example I wish to serve a WordPress blog on :8080 for HTTP and :8443 for HTTPS.I also want to force the admin access in SSL only (for that I’ll use the FORCE_SSL_ADMIN/FORCE_SSL_LOGIN )
but if siteurl and home variables are set to
https://www.domain.com:8080/myblog/
admin will always redirect to
https://www.domain.com:8080/myblog/
that won’t work, the correct secure URL is:
https://www.domain.com:8443/myblog/
It’s quite normal because this secure URL/port is precised nowhereI didn’t find a way to precise in WP a different URL or at least a specific HTTPS port for SSL access.
A bad solution is to set
siteurl=https://www.domain.com:8443/myblog/
and home=https://www.domain.com:8080/myblog/
With these settings, normal access via unsecure/HTTP will generate JavaScript, CSS requests on HTTPS (that eventually the browser will block) – it’s using server ressources for nothing.Is there a solution to allow WordPress to handle some differents URLs or ports for secure and unsecure??
- The topic ‘Secure URL and non standard HTTP/HTTPS ports’ is closed to new replies.