Timeline for What is the benefit of forcing a site to load over SSL (HTTPS)?
Current License: CC BY-SA 3.0
21 events
when toggle format | what | by | license | comment | |
---|---|---|---|---|---|
Nov 1, 2016 at 19:54 | vote | accept | Eric | ||
Jul 12, 2016 at 16:12 | comment | added | R.. GitHub STOP HELPING ICE | @DavidMulder: Again, take it elsewhere. | |
Jul 12, 2016 at 15:04 | comment | added | David Mulder | @R.. When a question asks for the benefits of doing something with the clear implication that the OP is challenging those benefits, it seems prudent to mention disadvantages as well. Bikeshedding is talking about something unimportant, this answer is actively contributing and promoting the centralization of the internet. (Not that I was planning a discussion, but at the point you called it a bikeshed-eque rant and an unrelated issue that was too much) | |
Jul 12, 2016 at 15:00 | comment | added | R.. GitHub STOP HELPING ICE | @DavidMulder: No, I'm stating that it's unrelated to the topic of the question or this answer. If you want to discuss that open a new question about whether use of HTTPS "contributes to the centralization of the internet" on an appropriate SE site. Or if you think it's actually relevant to the question (again: I don't) then write your own answer explaining your reasoning. | |
Jul 12, 2016 at 14:58 | comment | added | David Mulder | @R.. Are you implying that centralizing the internet is a minor thing compared to the benefits of SSL in situatiouns like the OP is talking about? | |
Jul 12, 2016 at 14:57 | comment | added | David Mulder | @jiggunjer You're absolutely right, I do not get how I could get that pointed out and not realize what you meant. | |
Jul 12, 2016 at 13:56 | comment | added | R.. GitHub STOP HELPING ICE | Can we please not turn the comments on this answer into an off-topic bikeshed-esque rant on unrelated issues? | |
S Jul 12, 2016 at 8:56 | history | suggested | Basil Bourque | CC BY-SA 3.0 |
Linked to Wikipedia for terms.
|
Jul 12, 2016 at 8:11 | comment | added | VLAZ | It seems we are presented with a dilemma - let's call it a two-sided coin. If the coin falls one way, the Internet gets decentralised and this is not a good thing. If the coin lands on the reverse, the we go for centralisation and doom the Internet to an eternity of collapse. Either way, the game is rigged. | |
Jul 12, 2016 at 6:30 | review | Suggested edits | |||
S Jul 12, 2016 at 8:56 | |||||
Jul 12, 2016 at 2:22 | comment | added | jiggunjer | @DavidMulder your first comment said "decentralization [...] not a good thing" | |
Jul 11, 2016 at 22:30 | comment | added | David Mulder | @R.. By using https you are contributing to the centralization of authority on the internet (you could of course use self signed certificates, but hardly anybody does that). I am not sure how that's a user hostile agenda, because centralization of power seems to be a long term danger to all users | |
Jul 11, 2016 at 21:39 | comment | added | R.. GitHub STOP HELPING ICE | @DavidMulder: Indeed that final comment is mostly unrelated to image-quality-lowering, though it could matter to them if you're serving high-res photos/wallpaper/etc. and your users end up inadvertently getting junk. On your second point I fail to see how "contributing to the decentralization of the internet" is "definitely not a good thing". I think you either accidentally said the wrong thing or you have a very user-hostile agenda... | |
Jul 11, 2016 at 21:14 | comment | added | David Mulder | Just noting, failure from 'protecting' your users from proxies lowering the quality of images seems like a pretty acceptable thing. Google Data Saver and the Opera Proxy are pretty neat services and help a lot in third world countries. Also note that by using https you're contributing to the decentralization of the internet which is definitely not a good thing. | |
Jul 10, 2016 at 21:22 | comment | added | Ionic | Just a small addition left, referer links won't be propagated to a another host. This can be considered as "security" feature. Just as an idea: If you have a content only side, which refers to another site, the target site could parse your referer link and adapt their content or even layout to the referer to act like your page and collect data or something like that. | |
Jul 10, 2016 at 2:27 | comment | added | R.. GitHub STOP HELPING ICE | FYI most if not all of my examples have actually been seen in the wild. | |
Jul 10, 2016 at 2:10 | comment | added | Nayuki | @Mike Not really. A full rewriting proxy can decode all the traffic and inject whatever new stuff it wants afresh. | |
Jul 8, 2016 at 23:55 | comment | added | ceejayoz | @Mike Not really. There's plenty of off-the-shelf software to do this, and it all handles decompression and recompression just fine. | |
Jul 8, 2016 at 23:36 | comment | added | Mike -- No longer here | But if the data is compressed, then such injection you describe may be difficult to produce. | |
Jul 8, 2016 at 21:17 | review | Suggested edits | |||
Jul 8, 2016 at 21:20 | |||||
Jul 8, 2016 at 15:46 | history | answered | R.. GitHub STOP HELPING ICE | CC BY-SA 3.0 |