In the most common configurations, when running your web app behind Nginx or Apache, your https:// request will get redirected to http://. Sometimes, you may want to rewrite all HTTP requests to HTTPS.
The Amazon Elastic Load Balancer (ELB) supports a HTTP header called X-FORWARDED-PROTO. All the HTTPS requests going through the ELB will have the value of X-FORWARDED-PROTO equal to “HTTPS”. For the HTTP requests, you can force HTTPS by adding a simple rewrite rule, as follows:
1. Nginx
In your nginx site config file check if the value of X_FORWARDED_PROTO is https, if not, rewrite it:
|
1
2
3
4
5
6
7
8
9
10
|
server {
listen 80;
....
location / {
if ($http_x_forwarded_proto != ‘https’) {
rewrite ^ https://$host$request_uri? permanent;
}
....
}
}
|
2. Apache
Same goes for Apache, add this rewrite rule to your site’s config file:
|
1
2
3
4
5
6
7
|
<VirtualHost *:80>
...
RewriteEngine On
RewriteCond %{HTTP:X–Forwarded–Proto} !https
RewriteRule ^.*$ https://%{SERVER_NAME}%{REQUEST_URI}
...
</VirtualHost>
|
3. IIS
Install IIS Url-Rewrite module, using the configuration GUI add these settings
|
1
2
3
4
5
6
7
8
9
10
11
|
<rewrite xdt:Transform=“Insert”>
<rules>
<rule name=“HTTPS rewrite behind ELB rule” stopProcessing=“true”>
<match url=“^(.*)$” ignoreCase=“false” />
<conditions>
<add input=“{HTTP_X_FORWARDED_PROTO}” pattern=“^http$” ignoreCase=“false” />
</conditions>
<action type=“Redirect” redirectType=“Found” url=“https://{SERVER_NAME}{URL}” />
</rule>
</rules>
</rewrite>
|
Revisions
- January 13, 2016 @ 15:19:31 [Current Revision] by admin
- January 13, 2016 @ 15:19:31 by admin
No comments yet.