51–60 of 136 posts
Lesser known HTTP feature that I love, instead of linking to resources like follows: http://static4.scirra.net/images/favicon.ico /> You should link as follows: The double forward slash will select the current protocol the page is being viewed on which means no security errors if you're switching between http/https!
Lesser known HTTP feature that I love, instead of linking to resources like follows: http://static4.scirra.net/images/favicon.ico /> You should link as follows: The double forward slash will select the current protocol the page is being viewed on which means no security errors if you're switching between http/https!
That is a neat trick, does it work on all browsers?
Lesser known HTTP feature that I love, instead of linking to resources like follows: http://static4.scirra.net/images/favicon.ico /> You should link as follows: The double forward slash will select the current protocol the page is being viewed on which means no security errors if you're switching between http/https!
That is a neat trick, does it work on all browsers?
Earlier quoted context omitted.
You know it's become a huge internet meme right? http://www.google.com.au/search?q=x+all+the+things&oq=x+... .
Does rampant theft make theft any more acceptable?
In order to "get credit" for all of the traffic that they send everywhere twitter had to develop a fairly elaborate system of redirections (built into t.co) to make sure that clicks from twitter.com ended up being sent out to the rest of the web with referer information.
It would be a real shame if everyone in the world had to develop a similar process.
Part of me thinks that browsers should start sending referer information even when you click on links for SSL sites, though this change would bring with it other problems.
It is not at all obvious (to me at least) what that best thing to do here is.
> On our production frontend machines, SSL/TLS accounts for less than 1% of the CPU load, less than 10KB of memory per connection and less than 2% of network overhead. This is too good to be true.
I assure you that it's true. I haven't reprofiled in that much detail since but I suspect that the numbers look even better now. Partly because computers are faster and partly because of software improvements.
Just Tuesaday, I sent an email around the company discussing SSL vulnerabilities, how they impact our product, and ways we can mitigate that. I've pulled out the parts specific to our product, but the rest may be interesting. I would love feedback on things I may have missed. FWIW, it doesn't instill great confidence in SSL, but it isn't completely horrible. ------------------------ 1. It is possible to pretend to be…
Says encrypt all the things...
isn't encrypted.
Lesser known HTTP feature that I love, instead of linking to resources like follows: http://static4.scirra.net/images/favicon.ico /> You should link as follows: The double forward slash will select the current protocol the page is being viewed on which means no security errors if you're switching between http/https!
For content that is already public but needs to be protected from modification like images and scripts couldn't it be hashed and the hash just sent with the page your viewing. Then the browser could download extra assets from an insecure source like a proxy or cdn and know that it hasn't been modified?