Bug #14990
Updated by Tom Morris over 5 years ago
Attempting to navigate to an unknown path should produce does not yield an error message. Examples where there is not currently the case include: error. https://workbench2.c97qk.arvadosapi.com/project/c97qk-j7d0g-4xans0bhlqiyrkv - For example, this works: https://workbench2.c97qk.arvadosapi.com/projects/c97qk-j7d0g-4xans0bhlqiyrkv This spins forever ("project" misspelled) https://workbench2.c97qk.arvadosapi.com/projects/c97qk-j7d0g-4xans0bhlqiyrk - misspelled): https://workbench2.c97qk.arvadosapi.com/project/c97qk-j7d0g-4xans0bhlqiyrkv This also spins forever (last character of uuid is missing) https://workbench2.c97qk.arvadosapi.com/projects/c97qk-j7d0g-4xans0bhlqiyrkk - missing): https://workbench2.c97qk.arvadosapi.com/projects/c97qk-j7d0g-4xans0bhlqiyrk This loads an empty project page instead of returning an error saying non-existent page, giving the impression that the project exists: Possibly relevant - https://stackoverflow.com/questions/32128978/react-router-no-not-found-route https://workbench2.c97qk.arvadosapi.com/projects/c97qk-j7d0g-4xans0bhlqiyrkk