Title: luhoide's Replies | WordPress.org

---

# luhoide

  [  ](https://wordpress.org/support/users/luhoide/)

 *   [Profile](https://wordpress.org/support/users/luhoide/)
 *   [Topics Started](https://wordpress.org/support/users/luhoide/topics/)
 *   [Replies Created](https://wordpress.org/support/users/luhoide/replies/)
 *   [Reviews Written](https://wordpress.org/support/users/luhoide/reviews/)
 *   [Topics Replied To](https://wordpress.org/support/users/luhoide/replied-to/)
 *   [Engagements](https://wordpress.org/support/users/luhoide/engagements/)
 *   [Favorites](https://wordpress.org/support/users/luhoide/favorites/)

 Search replies:

## Forum Replies Created

Viewing 1 replies (of 1 total)

 *   Forum: [Plugins](https://wordpress.org/support/forum/plugins-and-hacks/)
    In
   reply to: [[Robin Image Optimizer – Unlimited Image Optimization, WebP & AVIF] HTTP 422 error on PNG files during optimization](https://wordpress.org/support/topic/http-422-error-on-png-files-during-optimization/)
 *  Thread Starter [luhoide](https://wordpress.org/support/users/luhoide/)
 * (@luhoide)
 * [4 months, 2 weeks ago](https://wordpress.org/support/topic/http-422-error-on-png-files-during-optimization/#post-18830356)
 * Hello,
 * Thanks for your reply.
 * To clarify: on my side the files are correctly detected as PNG (image/png) in
   WordPress, and the requests to /wp-admin/admin-ajax.php return HTTP 200 (so there
   is no server-side block at this stage). The issue is that your optimization endpoint
   returns HTTP 422 for some standard PNG files (example: 1080×1350, ~1 MB) that
   were previously optimized successfully on the same site.
 * Given that you recently changed your optimization APIs, the timing strongly suggests
   a regression or stricter validation on your side (MIME detection / file header
   parsing / upload processing).
 * Please:
 * 1) check your API logs for my request and confirm which exact error code is returned(
   VALIDATION_ERROR / UPLOAD_FAILED / UNSUPPORTED_MIME_TYPE or other), and what 
   parameter/header triggered the 422;
 * 2) confirm whether the new API introduced stricter PNG parsing/validation (even
   if unintentionally);
 * 3) advise if there is a plugin update or setting I should apply to match the 
   new API requirements.
 * I can share a direct link to an affected PNG from my Media Library, or upload
   the file if you provide the preferred method.
 * Best regards,Luca
    -  This reply was modified 4 months, 2 weeks ago by [luhoide](https://wordpress.org/support/users/luhoide/).

Viewing 1 replies (of 1 total)