Avif images served with incorrect `Content-Type` header
Nobody has claimed this yet.
Assessment
- Difficulty
- 2/5
- Estimated time
- 1-3 hours
- Newbie friendliness
- 38/100
- Issue type
- Bug
- Clarity
- Clearly specified
- Activity status
- Stale
- Tech stack
- nginx, wordpress
- Domain
- devops, infrastructure
Research direction
Start by locating EasyEngine's generated Nginx server configuration and reviewing how MIME types are assigned for image extensions. Reproduce the issue with an AVIF image and inspect its response headers; done means AVIF responses use Content-Type: image/avif while existing WebP behavior remains correct.
Written by the indexing model from the issue text.
Description
Description
I am using EasyEngine to host a WordPress website that utilizes the Modern Image Formats plugin to convert images to WebP and Avif formats. While WebP images are served correctly, Avif images are being served with an incorrect Content-Type header (application/octet-stream instead of image/avif).
Steps to Reproduce:
- Install EasyEngine on a server.
- Create a WordPress site using EasyEngine.
- Install the Modern Image Formats plugin.
- Configure the plugin to convert images to WebP and Avif.
- Upload an image and observe the
Content-Typeheader for the generated Avif version.
Expected Behavior:
Nginx should serve Avif images with the Content-Type: image/avif header.
Actual Behavior:
Nginx is serving Avif images with the Content-Type: application/octet-stream header.
Additional Information:
- EasyEngine version:
EE 4.8.0 - Site having issue: https://privacysandbox-stories.com/
Suggested Solution:
Update EasyEngine's Nginx configuration to include the following line within the server block:
location ~* \.(avif)$ {
add_header Content-Type image/avif;
}- Dominant language
- PHP
- Stars
- 2.2k
- Forks
- 423
- PR merge metrics
- No merged PRs in 30d
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
More from EasyEngine/easyengine
-
Difficulty 1/5 Under an hour Newbie friendliness 70/100
EasyEngine/easyengine#1427 ·
-
Difficulty 4/5 3-5 days Newbie friendliness 25/100
EasyEngine/easyengine#1893 · 1 comment ·
-
Difficulty 3/5 1-2 days Newbie friendliness 25/100
EasyEngine/easyengine#1875 · 1 comment ·
-
Difficulty 4/5 3-5 days Newbie friendliness 35/100
EasyEngine/easyengine#1810 · 2 comments · 4 reactions ·
-
Difficulty 4/5 3-5 days Newbie friendliness 25/100
EasyEngine/easyengine#1800 · 2 comments ·
All issues in EasyEngine/easyengine
Similar issues
-
tooling
Difficulty 2/5 1-3 hours Newbie friendliness 75/100
-
UX
Difficulty 2/5 1-3 hours Newbie friendliness 70/100
ProfessionalWiki/NeoWiki#1525 ·
-
Difficulty 2/5 1-3 hours Newbie friendliness 75/100
-
Difficulty 1/5 Under an hour Newbie friendliness 90/100
OpenConext/OpenConext-engineblock#2122 ·
-
Bug
Difficulty 2/5 1-3 hours Newbie friendliness 70/100
Automattic/safe-publish#594 ·