POST /avatar/upload should validate image payload #96
Comments
|
Yeah, so, the profile server's worker was correctly detecting the error. However, the server did not see the error and would return 200 OK and a URL to where the image had supposedly been stored. The problem can be duplicated with: You need to obviously provide a valid Bearer token above, but if you do, that will return '201 Created' with a payload that has a url. The problem is that the response from the worker is gzipped, but the server expect uncompressed. Possibly just need to not asking for gzip is a fix: With the change above, that would now return HTTP 500 with:
Probably a little more detail than needed in that response, and a 400 level error would be better for bad input. |
|
I'm thinking of adding a |
If the body of the request doesn't look like image data (e.g.
{}) the request should fail.The text was updated successfully, but these errors were encountered: