![]() |
Automatically redirect to HTTPS
Only after a Firefox update did I realize that Flyertalk does not redirect to HTTPS before accepting login credentials. Very 1995! The site really should do that at the first hit since many people do not type in https:// and they may get non S by default.
|
Originally Posted by elCheapoDeluxe
(Post 28138585)
Only after a Firefox update did I realize that Flyertalk does not redirect to HTTPS before accepting login credentials. Very 1995! The site really should do that at the first hit since many people do not type in https:// and they may get non S by default.
:confused: |
The Technical Supportand Feedback forum is a better venue for hisissue, so it has been moved there.
JDiver, Co-Moderator, The Suggestion Box and Technical Support and Feedback fora |
We are working on it, and will have an update soon :)
|
Originally Posted by teddybear99
(Post 28153395)
The entire forum is not https://
:confused: |
I found this website bulletin board through Google because I was looking for something related to travel. It would not be available to Google or any search engine if it was secured website (hence the https://). Also people would not be able to view these boards without logging in either as they can now if it was a secured website. So your screen may show https://, but it is not a secured website, so your point is moot.
|
Originally Posted by teddybear99
(Post 28162301)
I found this website bulletin board through Google because I was looking for something related to travel. It would not be available to Google or any search engine if it was secured website (hence the https://). Also people would not be able to view these boards without logging in either as they can now if it was a secured website. So your screen may show https://, but it is not a secured website, so your point is moot.
Regarding the crawling, here is some info from the webmasters Google blog regarding HTTPS: https://webmasters.googleblog.com/20...y-default.html |
Originally Posted by elCheapoDeluxe
(Post 28179405)
There is a whole bunch of wrong in this. Not only does Google index HTTPS, Google gives a ranking boost to HTTPS sites. As for my screen showing HTTPS but not being secured I just don't think you understand what we're talking about. There is no relationship between https and requiring login. Those are two discreet things. We are talking transport here, and having a secure transport before authentication - not necessarially requiring authentication. If you DO process authentication you should have a secure transport, though, to protect user credentials.
Regarding the crawling, here is some info from the webmasters Google blog regarding HTTPS: https://webmasters.googleblog.com/20...y-default.html I'd also like to add that I had no idea FT even supported HTTPS until very recently, and it should definitely be, at the very least, the default option. |
| All times are GMT -6. The time now is 2:25 am. |
This site is owned, operated, and maintained by MH Sub I, LLC dba Internet Brands. Copyright © 2026 MH Sub I, LLC dba Internet Brands. All rights reserved. Designated trademarks are the property of their respective owners.