Project

General

Profile

Actions

Feature #8023

closed

Redirect to FQDM

Added by Derek Schrock about 7 years ago. Updated over 5 years ago.

Status:
Closed
Priority:
Low
Assignee:
-
Category:
Web Interface
Target version:
-
Start date:
10/28/2017
Due date:
% Done:

0%

Estimated time:
Plus Target Version:
Release Notes:

Description

When "WebGUI redirect" is unchecked from System->Advanced pfsense will redirect requests to http to https.

If you have an HTTPS cert installed with a FQDN as the commonname the redirect to https will request in a "Your connection is not secure" type message because your requested URL doesn't match the common name.

Could the redirect include the configured domain from System->General Setup.


Files

redirect-fqdn.patch (440 Bytes) redirect-fqdn.patch configure server_name in nginx config with host+domain redirect to server_name Derek Schrock, 10/28/2017 01:58 PM
Actions #1

Updated by Derek Schrock about 7 years ago

Possible fix see attached patch

Actions #2

Updated by Jim Pingle about 7 years ago

The problem with doing this is that you do not know that the hostname exists in DNS and is working properly.

It would have to be an option and default to off. Or perhaps the redirect option could change from a checkbox to a selection list with three choices: Redirect by IP Address (default), Redirect by Hostname, No Redirect.

Actions #3

Updated by Derek Schrock about 7 years ago

Good point.

Would it be acceptable to do all this transparently inside nginx conf leaving the interface as is? If ip redirect to https://ip otherwise assume host and redirect to the configured host+domain? I think I have a working patch for this.

Actions #4

Updated by Jim Pingle over 5 years ago

  • Category set to Web Interface
  • Status changed from New to Closed

At some point this must have changed. If I go to http://<fqdn> it redirects me to https://<fqdn>. It works fine for me with a Let's Encrypt cert.

Actions

Also available in: Atom PDF