Redirect from HTTP to HTTPS using meta redirects

Go to file

AJ ONeal 8d55d4910e v1.0.0		2015-07-07 17:19:44 -06:00
.gitignore	Initial commit	2015-06-19 09:15:45 -06:00
LICENSE	Initial commit	2015-06-19 09:15:45 -06:00
README.md	v1.0.0	2015-07-07 17:19:44 -06:00
example.js	v1.0.0	2015-07-07 17:19:44 -06:00
index.js	v1.0.0	2015-07-07 17:19:44 -06:00
package.json	v1.0.0	2015-07-07 17:19:44 -06:00

README.md

redirect-https

Redirect from HTTP to HTTPS using meta redirects

Installation and Usage

npm install --save redirect-https

'use strict';

var express = require('express');
var app = express();

app.use('/', require('redirect-https')({
  body: '<!-- Hello Mr Developer! Please use HTTPS instead -->'
}));

module.exports = app;

Options

{ port: 443           // defaults to 443
, body: ''            // defaults to an html comment to use https
, trustProxy: true    // useful if you haven't set this option in express
}

This module will call next() if the connection is already tls / https.
If trustProxy is true, and X-Forward-Proto is https, next() will be called.
If you use {{URL}} in the body text it will be replaced with the url

Demo

'use strict';

var http = require('http');
var server = http.createServer();
var securePort = 8443;
var insecurePort = process.argv[2] || 8080;

server.on('request', require('redirect-https')({
  port: securePort
, body: '<!-- Hello! Please use HTTPS instead -->'
, trustProxy: true // default is false
}));

server.listen(insecurePort, function () {
  console.log('Listening on http://localhost.daplie.com:' + server.address().port);
});

Why meta redirects?

When something is broken (i.e. insecure), you don't want it to kinda work, you want developers to notice.

Using a meta redirect will break requests from curl and api calls from a programming language, but still have all the SEO and speed benefits of a normal 301.

<html><head>
<meta http-equiv="refresh" content="0;URL='https://example.com/foo'" />
</head><body>
<!-- Hello Mr. Developer! Please use https instead. Thank you! -->
</html>

Other strategies

If your application is properly separated between static assets and api, then it would probably be more beneficial to return a 200 OK with an error message inside

Security

The incoming URL is already URI encoded by the browser but, just in case, I run an html escape on it so that no malicious links of this sort will yield unexpected behavior:

http://localhost.daplie.com:8080/"><script>alert('hi')</script>
http://localhost.daplie.com:8080/';URL=http://example.com
http://localhost.daplie.com:8080/;URL=http://example.com