-
Notifications
You must be signed in to change notification settings - Fork 107
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Optimization detective can return non-ascii characters in the Link header, breaking some reverse proxies and HTTP standards. #1775
Comments
Hey 👋, |
Here's the relevant code: performance/plugins/optimization-detective/class-od-link-collection.php Lines 247 to 278 in 90be052
|
@AhmarZaidi How's it going with this? |
Hey @westonruter, I've created a Draft PR for this issue: #1802 |
Bug Description
Optimization detective can return non-ascii characters in the Link header, breaking some reverse proxies and HTTP standards.
Steps to reproduce
Example link with Hebrew chars:
https://testsite.com/wp-content/uploads/2025/01/חנות-scaled.avif
If this is added to optimization detection, for example via image prioritizer, it will cause the response header of the page to include:
HTTP headers should contain only ISO-8859-1 chars and this breaks it, the url path should be encoded.
The text was updated successfully, but these errors were encountered: