Skip to content
This repository has been archived by the owner on Apr 7, 2021. It is now read-only.

Invalid upstream response (201) #105

Open
jomo opened this issue Jun 20, 2016 · 1 comment
Open

Invalid upstream response (201) #105

jomo opened this issue Jun 20, 2016 · 1 comment

Comments

@jomo
Copy link
Contributor

jomo commented Jun 20, 2016

This image doesn't show up because the server returns a 201:

![201 test](https://img-any-status.herokuapp.com/201)

201 test

201 is typical for POST or PUT requests, but I can't find anything that states it would be invalid as response to GET.

I think #77 should have fixed that and can't actually find the code for the error message in the sources, but I thought I'd report here since it seems to be related to camo.

@jomo
Copy link
Contributor Author

jomo commented Jun 20, 2016

camo forwards the status code it receives, see here. Possibly it's whatever GitHub places in front of it? Google doesn't return anything meaningful for that error message, either.

Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant