An understanding of how WP stores content is important. Pages/posts’ content is stored in the database. Media files are stored in the uploads folder, and the pointers to the media (their URLs) are stored in the database. (Media files are just another type of post/page.) The base URL for your site is stored in the … Read more
If you are generating a self signed cert, you can do both the key and cert in one command like so: openssl req -nodes -new -x509 -keyout server.key -out server.cert Oh, and what @MadHatter said in his answer about omitting the -des3 flag.
You can combine this into one server block like so: server { listen 80; listen 443 default_server ssl; # other directives } Official How-To
The [R] flag on its own is a 302 redirection (Moved Temporarily). If you really want people using the HTTPS version of your site (hint: you do), then you should be using [R=301] for a permanent redirect: RewriteEngine on RewriteCond %{SERVER_PORT} !^443$ RewriteRule ^/(.*) https://%{HTTP_HOST}/$1 [NC,R=301,L] A 301 keeps all your google-fu and hard-earned pageranks … Read more
Correct way in new versions of nginx Turn out my first answer to this question was correct at certain time, but it turned into another pitfall – to stay up to date please check Taxing rewrite pitfalls I have been corrected by many SE users, so the credit goes to them, but more importantly, here … Read more
First, you should not customize anything between # BEGIN WordPress and # END WordPress, it’s just not a good practice. You should add your own rules above WP rules. And you should also make use of some flags, like “L”. # BEGIN Custom <IfModule mod_rewrite.c> Options All -Indexes RewriteEngine On RewriteBase / RewriteCond %{HTTPS} !on … Read more
Your rewrite conditions, line 4 to 6 in your code, apply when https is active, so you are redirecting from https to https. Consquently you should change the conditions to check, if https is not active, ergo !on and !^443$ and !https. Additionally I’m not sure about the rule RewriteRule .* – [E=WPR_SSL:-https], probably something … Read more
Solved : WP Engine :rolleyes – When using WPEngine you have to ask them to manually exempt whatever cookies you set otherwise the caching they use will essentially render an empty string and make it look like the cookie wasn’t set
Sounds like you switched over to HTTPS and your site assets aren’t loading. Here are a few things you can try. Update your site address by going to Admin > Settings > General and making sure you have https instead of just http in the URL fields Add define(‘FORCE_SSL_ADMIN’, true); to wp-config.php Change any static … Read more
@Ooker It’s the Jetpack that is serving you the images on https. If you’d turn off the Photon add-on from Jetpack you should be able to get images served over http from your own server. Also if you turn off Photon, images won’t be served from CDN anymore, so you might have to figure that … Read more