andrieslouw
commented
2 years ago Our automated system to block abuse flagged some traffic, and made rules that blocked a bit too much. I'll spare you the details, but somewhere a regular expression got a bit too inclusive, and your request payload was matching this.
The 204 is send by this system as a last resort to prevent users from hogging resources, it's the fastest way of telling the client to keep going and ignore the response, but normal use should not trigger this.
Should be fixed now, could you verify this?
ebaynaud
Hi there, thanks a lot for your awesome work.
Starting today, I keep getting 204 responses when loading images from my app pages (app.alobees.com):
If I open the image URL directly in the browser, the image displays well and refreshing the initial page, I get a 200 and it now shows better:
But all other images still get 204. Any idea?