Forum Replies Created

Viewing 1 replies (of 1 total)
  • Thread Starter luhoide

    (@luhoide)

    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 3 months ago by luhoide.
Viewing 1 replies (of 1 total)