Skip to content

[Bug Hunt - NEW BUG]504 Gateway Time-out #192

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Closed
twicoder opened this issue Aug 24, 2017 · 2 comments
Closed

[Bug Hunt - NEW BUG]504 Gateway Time-out #192

twicoder opened this issue Aug 24, 2017 · 2 comments

Comments

@twicoder
Copy link

  1. Try to open URL: http://community-app.topcoder.com/challenges/10000090909090909090909090909
  2. Long time no response

2017-08-24 10 02 41

@birdofpreyru
Copy link
Collaborator

I'll accept it with 1 point, though it is kind of dublicate of #190

@elfman
Copy link
Contributor

elfman commented Aug 25, 2017

This bug is different with #190. It's cause by the server, server does not return anything response when challengeId is wrong, which make the link time out.
Except: Server returns 'null' or other error msg when challenge id is not exist. At least, don't make the link time out.

Edit: Sorry, I make a mistake, the gateway timeout is caused by server rendering failure, not by backend

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

No branches or pull requests

3 participants