Sunday, September 16th, 2018
Saturday, September 15th, 2018
Tuesday, August 28th, 2018
Monday, August 27th, 2018
Sunday, August 26th, 2018
Saturday, August 25th, 2018
Friday, August 24th, 2018
Sunday, August 19th, 2018
Thursday, August 16th, 2018
A great post by Tim following on from the post by Eric I linked to last week.
Is a secure site you can’t access better than an insecure one you can?
He rightly points out that security without performance is exlusionary.
…we’ve made a move to increase the security of the web by doing everything we can to get everything running over HTTPS. It’s undeniably a vital move to make. However this combination—poor performance but good security—now ends up making the web inaccessible to many.
Security. Performance. Accessibility. All three matter.
Monday, August 13th, 2018
Sunday, August 12th, 2018
Tuesday, August 7th, 2018
This is a heartbreaking observation by Eric. He’s not anti-HTTPS by any stretch, but he is pointing out that caching servers become a thing of the past on a more secure web.
Can we do anything? For users of up-to-date browsers, yes: service workers create a “good” man in the middle that sidesteps the HTTPS problem, so far as I understand. So if you’re serving content over HTTPS, creating a service worker should be one of your top priorities right now, even if it’s just to do straightforward local caching and nothing fancier.
What an excellent question! And what an excellent bit of sleuthing to get to the bottom of it. This is like linguistic spelunking on the World Wide Web.
Oh, and of course I love the little sidenote at the end.
Tuesday, July 31st, 2018
Saturday, July 28th, 2018
Saturday, July 21st, 2018
Friday, July 20th, 2018