User tests: Successful: Unsuccessful:
Since the current global config "Force HTTPS" warning message doesn't say much to user, this PR makes the message show the real problem.
None.
@brianteeman please check
Status | New | ⇒ | Pending |
Labels |
Added:
?
?
|
Category | ⇒ | Administration Components Language & Strings |
Labels |
Removed:
?
|
@andrepereiradasilva to be able to test this PR, you need a server with SSL configuration issues.
Any idea how to create those issues
To create an issue do this:
CURLOPT_PROXY => 'nohost.local',
I have tested this item
Tested successfully.
The test instructions in the last message are the easiest way to create a not working HTTPS situation to be able to see the error message.
I have tested this item
Tested on Localhost:
Message:
HTTPS has not been enabled as it is not available on this server. HTTPS connection test failed with the following error: Failed to connect to localhost port 443: Connection refused
Status | Pending | ⇒ | Ready to Commit |
Labels |
RTC
Labels |
Milestone |
Added: |
Status | Ready to Commit | ⇒ | Fixed in Code Base |
Closed_Date | 0000-00-00 00:00:00 | ⇒ | 2016-11-10 09:03:37 |
Closed_By | ⇒ | rdeutz |
@andrepereiradasilva any ideas on creating config issues for HTTPS?
This comment was created with the J!Tracker Application at issues.joomla.org/tracker/joomla-cms/12465.