Some binary file types from /wp endpoint return 403 error
See original GitHub issueWhen using CSS file from /wp
endpoint that references image file for background, I noticed that image file is returning error with 403 status code. After little manual testing, it looks like this is happening for more binary file types.
Here are some examples:
- JPG (original)
- PNG (original)
- GIF (original)
- WOFF2 (original; but other font types work)
- SWF (original)
- XAP (original)
These are example file types I have found and all those file types work on /npm
endpoint (example).
Issue Analytics
- State:
- Created 6 years ago
- Comments:7 (5 by maintainers)
Top Results From Across the Web
How to Fix a 403 Forbidden Error on Your WordPress Site
The 403 Forbidden error means that your server is working, but you no longer have permission to view all or some of your...
Read more >403 Forbidden Error: What It Is and How to Fix It - Airbrake Blog
A detailed explanation of what a 403 Forbidden Error response is, including troubleshooting tips to help you resolve this error.
Read more >How to Fix the 403 Forbidden Error in WordPress - WPBeginner
Often the 403 error is caused by a corrupt .htaccess file in your WordPress site. Repairing this file is quite easy. First you...
Read more >Error Http 403 in /wp-json/ | WordPress.org
A 403 HTTP status response means “Forbidden Request”, meaning something is blocking access to the REST API on your website (see: Is WordPress...
Read more >Amazon Web Services - Resolving 403 Forbidden Error When ...
In this article, we will resolve the error 403 forbidden that occurs while accessing a public API gateway API from within a Virtual...
Read more >Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start FreeTop Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found
Top GitHub Comments
Awesome! Thank you both for speedy response and resolution.
@dimadin The change was deployed, all linked files are now working