calisun
The 6 month/10 year comparison was just a play on words or a type of pun on my part (smile).
The point is that expected behavior of "Force" Secure connection, is not how it is actually behaving.
But that is interpretable, the idea at the time it was implemented may have been to force users to make a secure connection ie using https manually, rather than the system forcing the https connection. Granted that the behviour is really to block http connections, so the wording is in error or ambiguous or there was an error in coding or the actual coders intention.
The bug comments seem to suggest no action will be taken at present due to other php related coding efforts etc.
So my point really was that a very easy fix exists & has existed for at least 12 years (looking at dates on files), so a simple custom template would take 3 - 5 minutes to implement.
A more permanent "base system" fix would probably be a template anyway.
I recall having used this answer/method in the past quite satisfactorily.
No need to wait for someone else to come up with an answer.
21 Replies
6134 Views