When using API to upload file via URL, the upload url sometimes returns 502 status code

unknown

I'm using the file upload API to upload files to user accounts via a URL. When I post to the upload_url provided by the API endpoint (e.g. "users/1234/files?as_user_id=1234"), it usually returns a 201 HTTP status code. However, I sometimes get a 502 HTTP status code & HTML that looks like this:

502 Bad Gateway

502 Bad Gateway

---

nginx

When I check the progress URL for the upload later, though, it shows that the upload has completed successfully. So it looks like the 502 status code does not indicate an error situation? How do I detect that errors that occur for the post to the upload_url, then?

James

 @tshek  

The 502 Bad Gateway status means that something went wrong. MDN says it's usually something that the user cannot fix, but I can think of at least one place it might be. You might check to make sure that all of the file got transferred correctly and is usable when you download it.

Is there anything specific about when it works and when it doesn't?

For example, does it only happen with larger files? If you're trying to send the contents of a file in the URL, rather than as a separate multipart/form attachment, then you might get the 502 error because the URL is too long.

As far as checking, you can save those that fail and later check the progress URL like you're saying.

I would try to track down the cause of the 502, but sometimes it really is a problem on the server and there's nothing you can do about it. Don't just ignore it and assume everything was successful, though.