Browsers barely care what HTTP status code your web pages are served with

Post by Jiocus » Mon, Aug 14, 2023, 12:17 AM UTC

javajosh wrote: post #118

Jiocus wrote: post #112

Earlier quoted context omitted.

base64 inline your image with the HTML and you should be well past that threshold. It's preferable to not make additional requests (like for an image) on an error page - in case the requested server is at fault - breaking the error page.

Fun fact: did you know you can inline an image without base64 encoding it? Use svg you can inline the markup using a data url without base64 encoding. This is how I do my favicons at simpatico[0]: " > What's nice is that this opens up the possibility to generate dynamic favicons really easily using only string interpolation. 0 - https://simpatico.io/svg.md

Yes, it makes a lot more sense to use svg when the image content is a good fit for the svg format, like most icons and line-drawn graphical elements.

Thanks for the tip, and the many examples on your site!

Post by lcnPylGDnU4H9OF » Tue, Aug 15, 2023, 3:10 AM UTC

dredmorbius wrote: post #205

lcnPylGDnU4H9OF wrote: post #202

Earlier quoted context omitted.

Even their blog has such dead links. I just happened to notice that other URLs included the year, so I tracked that one down to see if that’s all what was needed. Of course, forgetting about that little backwards compatibility is easy, especially considering it’s a personal blog and they likely have other personal things to worry about. I was just amused by the irony in context. I otherwise appreciated the read. :)

If you happen to remember any of those, drop her a line. I'm pretty sure Deirdre's fairly meticulous about that sort of thing.

I should be able to find it. It was an aggregate post from 2014 titled something like “stuff I wrote this year” which is how I found the year for the post in question.

Re: Browsers barely care what HTTP status code your web pages are served with

Re: Browsers barely care what HTTP status code your web pages are served with