-
Notifications
You must be signed in to change notification settings - Fork 481
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
404 Not Found - Browser Gets Forwarded to /404.xhtml #2367
Comments
👍 |
Turned to StackOverflow in a quest for answers. |
The answer by @lincolnthree who created PrettyFaces is obviously worth checking out! |
This is not just about seeing the wrong URL - it breaks semantics of the web, because instead of giving an error response to the browser, this is just showing the error text. The browser is told to find the answer to a bogus request at /404.xhtml and because that is there, the browser 'thinks' the request was handled correctly ( This goes for 403 responses too. Please put this issue on the roadmap. |
Yes, regarding the HTTP status code, you should still send '404 NOT FOUND' when forwarding to the error page. |
This is also happening for the 403 pg, as found in #2838. |
This has been fixed in the widgets branch. |
@sekmiller showed me how this works with "/loginpage.xhtml" for example and how the Shib code should be modified after edf12fb and related commits are merged into "develop". I asked him not to touch the Shib code in the widgets branch since it will only lead to a merge conflict on pull request #3025. The bottom line for @kcondon is that this might need to be retested as we integrate multiple branches into "develop". |
@scolapasta if https://github.com/IQSS/dataverse/tree/2469-widgets gets merged before https://github.com/IQSS/dataverse/tree/2939-shib (pull request #3025) shouldn't a new issue get opened to have the Shib code use the new sendError method that will only be available once the 2469-widgets branch is merged? I'm asking because at #3025 (comment) @eaquigley wrote "Good on my end. Passing to @kcondon to merge." |
Works, closing, error is presented but URL is preserved and correct http code is returned. |
When looking at how our site handles URLs that are not found -- AKA, 404 Not Found Error -- I noticed that the bad URL is not retained in the browser window, instead it gets forwarded to the URL /404.xhtml. Other sites don't forward you, so that you can see what the bad URL is -- maybe it was a typo, and you can easily fix it.
Related(?) to #1057.
The text was updated successfully, but these errors were encountered: