You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I have deployed the solution with auto-WebP activated, but it's not working.
The "Accept" header is being sent with the webp type included and the server is responding with "Content-Type: image/webp" (if I try to save the image, the browser saves it with webp extension).
The problem is that the image is exactly the original jpg file, it's not being converted to WebP. If I add a WebP filter ("filters:format(webp)"), then it works as expected.
How could I debug this and what could be the reason?
Thanks!
The text was updated successfully, but these errors were encountered:
Thanks for checking, can you then confirm that this is actually not working?
I didn't mark it as a bug because it's strange that a feature that so many people is using doesn't work
I can reproduce this issue. I do see the size difference in the resulting image with AutoWebP enabled vs filters:format(webp). So I have assigned this to our team for further debugging.
@anibarro, we have updated our solution, the issue has been fixed. If you still see the issue with the latest version (v6.0.0), please feel free to reopen the issue.
Hi,
I have deployed the solution with auto-WebP activated, but it's not working.
The "Accept" header is being sent with the webp type included and the server is responding with "Content-Type: image/webp" (if I try to save the image, the browser saves it with webp extension).
The problem is that the image is exactly the original jpg file, it's not being converted to WebP. If I add a WebP filter ("filters:format(webp)"), then it works as expected.
How could I debug this and what could be the reason?
Thanks!
The text was updated successfully, but these errors were encountered: