Skip to content

[$30] - [Bug Hunt - NEW BUG]Unexpected URL is not handled properly #190

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 · 5 comments
Closed

[$30] - [Bug Hunt - NEW BUG]Unexpected URL is not handled properly #190

twicoder opened this issue Aug 24, 2017 · 5 comments

Comments

@twicoder
Copy link

  1. try to open url: http://community-app.topcoder.com/challenges/*
  2. Page body is not shown

2017-08-24 9 59 01

@birdofpreyru birdofpreyru changed the title [Bug Hunt - NEW BUG]Unexpected URL is not handled properly [$20] - [Bug Hunt - NEW BUG]Unexpected URL is not handled properly Aug 24, 2017
@birdofpreyru
Copy link
Collaborator

Accepted, 3 points.

Expected Fix

The routing should be corrected, to ensure that when a non-digital challenge ID is supplied in such route, it renders 404 Error page.

@birdofpreyru birdofpreyru changed the title [$20] - [Bug Hunt - NEW BUG]Unexpected URL is not handled properly [$30] - [Bug Hunt - NEW BUG]Unexpected URL is not handled properly Aug 24, 2017
@birdofpreyru
Copy link
Collaborator

Please also take into account #192 which is also caused by incorrect challenge ID used in URL. That should also render 404 error page.

@elfman
Copy link
Contributor

elfman commented Aug 25, 2017

assign myself

elfman added a commit to elfman/community-app that referenced this issue Aug 25, 2017
@elfman
Copy link
Contributor

elfman commented Aug 25, 2017

PR arised.
#192 is not fixed in this PR, server should return something when chanlengeId is not exist, currently it keeps the link waiting and nothing response.

@birdofpreyru
Copy link
Collaborator

@ajefts @skyhit See the last comment. It looks like when we pass a non-existing challenge ID into the backend, it just stucks, rather than returning and error (404?) right away.

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