News for hackers. Stuff that matters.

A comment on In protest of the web{*} bulldozer, a response to websocket port scanning. Parent comment

Re:In protest of the web{*} bulldozer, a response to websock... by uryga on Wednesday May 20, 2020 @06:00PM (#23252434)
> safari both refuses to render webp and pretends to accept them

weird, i haven't had that issue! i run a site that's set up¹ to redirect image requests to a WebP version if the Accept header allows it; half our team uses Macs w/ Safari and no one reported any issues with images.

---

¹ wordpress + webp-express: https://github.com/rosell-dk/webp-express i guess it's possible they special-case Safari, i'll check later

[ Parent | on HN ]
Re:In protest of the web{*} bulldozer, a response to websock... by chipperyman573 on Wednesday May 20, 2020 @06:05PM (#23252502)
It could've been my setup, to be honest I had just finished fixing all the pseudo classes and was kind of frustrated and decided to just switch to png after I couldn't figure it out in 5 minutes hahaha

But whatever the case is, Safari definately does not support webp and special exceptions need to be made to support this edge case.

[ Parent | on HN ]
Re:In protest of the web{*} bulldozer, a response to websock... by cookiengineer on Thursday May 21, 2020 @12:23AM (#23254777)
> https://caniuse.com/#search=webp

Nope you are right, when reading the linked issues, safari doesn’t have webp support.

[ Parent | on HN ]
Re:In protest of the web{*} bulldozer, a response to websock... by ComputerGuru on Thursday May 21, 2020 @03:08AM (#23255625)
Yeah, but that’s not the issue/question. Not supporting webp is fine, the important thing is that it doesn’t send an accept header that includes it. I don’t believe it does.
[ Parent | on HN ]
Re:In protest of the web{*} bulldozer, a response to websock... by uryga on Thursday May 21, 2020 @10:26AM (#23258722)
just had a friend with a Mac test it. when requesting foo.jpg (from an <img> tag), it sends:

  Accept: image/png, image/svg+xml, image/*;q=0, video/*;q=0.8, */*;q=0.5
the server responds with foo.jpg.

i also tested it in Firefox, which sends:

  Accept: image/webp, */*
the server responds with foo-converted.webp.

honestly, i'm not entirely sure how

  image/*;q=0
  */*
etc are handled, but it works; i also briefly looked at the plugin's source, and i haven't found any special handling for Safari. btw, here's a test page linked in their docs: http://toste.dk/rh.php

---

edit: looking at the generated .htaccess, it appears that WebP is served only if Accept contains an explicit `image/webp` (no wildcards), so that explains it.

[ Parent | on HN ]