Skip to main content

Wordpress ReverseProxy HTTPS

How to make  Wordpress use HTTPS scheme when behind a ReverseProxy

I host Dockerized Wordpress. That means there is a front ReverseProxy that terminates the SSL tunnel and Proxies the requests to the Dockerized Wordpress through clear HTTP.

When a Wordpress is queried through clear HTTP, it builds all its assets URLs with HTTP scheme.

I want the  Dockerized Wordpress to builds all its assets URLs with HTTPS scheme.

Set the header "X-Forwarded-Proto" to the "https" value

In order to achieve that, I have to fool it (to lie) and pretend it has been queried through  HTTPS instead of clear HTTP.

For that, on the Dockerized Apache, I have to artificially set the header "X-Forwarded-Proto" to the "https" value.

In the ".htaccess" I have to :

  # Artificially set "X-Forwarded-Proto" to "https"
  RequestHeader set X-Forwarded-Proto "https"
  RequestHeader set X-Forwarded-Port "443"
  # following is standard Wordpress htaccess rules
  RewriteEngine On
  RewriteRule .* - [E=HTTP_AUTHORIZATION:%{HTTP:Authorization}]
  RewriteBase /
  RewriteRule ^index\.php$ - [L]
  RewriteCond %{REQUEST_FILENAME} !-f
  RewriteCond %{REQUEST_FILENAME} !-d
  RewriteRule . /index.php [L]


And in the "wp-config.php" file:

$_SERVER['HTTPS'] = 'on';

Popular posts from this blog

npm run build base-href

Using NPM to specify base-href When building an Angular application, people usually use "ng" and pass arguments to that invocation. Typically, when wanting to hard code "base-href" in "index.html", one will issue: ng build --base-href='' I used to build my angular apps through Bamboo or Jenkins and they have a "npm" plugin. I got the habit to build the application with "npm run build" before deploying it. But the development team once asked me to set the "--base-href=''" parameter. npm run build --base-href=' did not set the base href in indext.html After looking for a while, I found where it says: You need to use −− to pass arguments to npm scripts. This did the job! The command to issue is then: npm run build -- --base-href='

Jenkins invalid privatekey

Publish over SSH, Message "invalid privatekey:" With quite recent (June-July 2020) installations of Jenkins and OpenSSH, I have the following error message when using the "Deploy overs SSH" Jenkins plug-in and publishing artifacts to the target overs SSH: jenkins.plugins.publish_over.BapPublisherException: Failed to add SSH key. Message [invalid privatekey: [B@d8d395a] This problem seems to be referenced here: Just regenerate a key with the right parameters To solve it: ssh-keygen -t rsa -b 4096 Or ssh-keygen -t rsa -b 4096 -m PEM

Emacs Pulumi LSP

Install Pulumi Emacs Mode The source code is on At the very bottom of the page are the instructions on how to install. You Need to have make installed. $ make install emacs-client mkdir -p ./bin go build -ldflags "-X" -o ./bin -p 10 ./cmd/... go: downloading v3.53.1 ... ... ... go install -ldflags "-X" ./cmd/... mkdir -p editors/emacs/bin cd editors/emacs && emacs -Q --batch --eval "(progn (setq package-user-dir \"$(pwd)/bin\" \ package-archives '((\"melpa\" . \"\") \