200 status code on 404 pages
Categories
(Taskcluster :: UI, defect)
Tracking
(Not tracked)
People
(Reporter: tarek, Unassigned)
Details
This call
$ curl https://tools.taskcluster.net/v1/taskdelwkhdqwlhjdwq
Returns a page that claims it's a 404, but the response status code is a 200.
Any 404 route should set the status code to 404 for the client code to pick it
|
||
Comment 1•7 years ago
|
||
It's because of the way that is hosted as a static page -- our new hosting does this better.
|
|
||
Comment 2•7 years ago
|
||
Hm, although
https://taskcluster-ui.herokuapp.com/foo/bar
says "404" right at the top, and isn't.
Hassan, maybe that should just say "not found" or something, so as not to pretend an HTTP response code that didn't occur?
|
||
Comment 3•6 years ago
|
||
I think this is still a problem even the most recent taskcluster in other configurations?
I just got a 200 status result for a 404 page at https://firefox-ci-tc.services.mozilla.com/v1/task/gecko.v2.mozilla-central.nightly.latest.firefox.linux64-opt/artifacts/public/build/target.jsshell.zip while trying to figure out how to unbreak searchfox in bug 1595492. I tried this URL because trying to update https://index.taskcluster.net/v1/task/gecko.v2.mozilla-central.nightly.latest.firefox.linux64-opt/artifacts/public/build/target.jsshell.zip to https://firefox-ci-tc.services.mozilla.com/api/index/v1/task/gecko.v2.mozilla-central.nightly.latest.firefox.linux64-opt/artifacts/public/build/target.jsshell.zip nets me an actual 404 status code.
|
|
||
Comment 4•6 years ago
|
||
That's a UI page, just like before. I had a good idea in comment 2 :)
The URL you want is https://firefox-ci-tc.services.mozilla.com/api/index/v1/task/gecko.v2.mozilla-central.nightly.latest.firefox.linux64-opt/artifacts/public/build/target.jsshell.zip
|
|
||
Comment 6•6 years ago
|
||
It'd be great to go a step further than saying "not found" and link to documentation that explains the general URL scheme of the domain and/or a link to documentation that helps you figure out the right URL for what you want. And/or what route is actually applying and what it's intended to do.
For my bad URL, there are 6 path segments and it's not clear at what point the route went bad. It seems like maybe it was at the very root of the domain?
|
|
||
Comment 7•6 years ago
|
||
I think this confusion is mostly in transitioning from the legacy URL format to the current URL format, so in a week or two it will be vanishingly infrequent.
|
||
Comment 8•6 years ago
|
||
Description
•