- News
- Reviews
- Bikes
- Accessories
- Accessories - misc
- Computer mounts
- Bags
- Bar ends
- Bike bags & cases
- Bottle cages
- Bottles
- Cameras
- Car racks
- Child seats
- Computers
- Glasses
- GPS units
- Helmets
- Lights - front
- Lights - rear
- Lights - sets
- Locks
- Mirrors
- Mudguards
- Racks
- Pumps & CO2 inflators
- Puncture kits
- Reflectives
- Smart watches
- Stands and racks
- Trailers
- Clothing
- Components
- Bar tape & grips
- Bottom brackets
- Brake & gear cables
- Brake & STI levers
- Brake pads & spares
- Brakes
- Cassettes & freewheels
- Chains
- Chainsets & chainrings
- Derailleurs - front
- Derailleurs - rear
- Forks
- Gear levers & shifters
- Groupsets
- Handlebars & extensions
- Headsets
- Hubs
- Inner tubes
- Pedals
- Quick releases & skewers
- Saddles
- Seatposts
- Stems
- Wheels
- Tyres
- Health, fitness and nutrition
- Tools and workshop
- Miscellaneous
- Tubeless valves
- Buyers Guides
- Features
- Forum
- Recommends
- Podcast
Add new comment
6 comments
Double post
Another advantage of https is that it makes it harder for your company's IT department to tell exactly what you're posting on road.cc. If they didn't already have a keylogger installed.
Yes, but they can still tell which site you're visiting (you need a VPN to get round that). Actually, lots of companies will install a root certificate into all their equipment so that they can do a MITM (Man in the Middle) attack and thus see all your web traffic in the clear.
This probably has something to do with a change to Google's Chrome browser that means it's going to start flagging non-HTTPS sites as insecure.
I don't think it's pointless, as it means log-in details will now be encrypted.
Encrypting sensitive information (e.g. log-in details) is one aspect of it, but I'm a firm believer in using HTTPS for everything by default. I didn't notice that Road.cc didn't force HTTPS, but then I've been using the "HTTPS Everywhere" extension for a long time (it's produced by the Electronic Frontier Foundation - EFF.org).
The problem with using plain HTTP is that anyone between your browser and the website can intercept and change the web-pages. BT famously conducted a secret trial of the PHORM technology to change the adverts displayed on customers' browsers: https://en.wikipedia.org/wiki/Phorm . Using HTTPS prevents those kind of shenanigans.
Nice work.
Can't you fix the "bookmarked http" issue by doing a simple redirect?
I use the following snippet in NGINX web servers to do it:
location / {
return 301 https://$server_name$request_uri;
}
That way any http request will just get translated to the same url over https (the 301 code is a permanent redirect so hopefully the browser will update its bookmark).