Skip to content
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

Report 404 as an error on the source page instead of destination #17

Open
mthuurne opened this issue Jun 19, 2019 · 2 comments
Open

Report 404 as an error on the source page instead of destination #17

mthuurne opened this issue Jun 19, 2019 · 2 comments
Labels
enhancement New feature or request

Comments

@mthuurne
Copy link
Member

When a resource is not found (HTTP status 404), this is reported as an error on a non-existing page. Typically these problems are caused by broken links though, which are located on the referring page. So the report would be easier for the user to process if 404's are included in the referrer's section.

@mthuurne mthuurne added the enhancement New feature or request label Jun 19, 2019
@mthuurne
Copy link
Member Author

mthuurne commented Sep 9, 2021

Maybe the same applies to other client error (4xx) status codes: if the server thinks the client is wrong in asking these, then the problem should be reported on the page(s) that generated the request.

Perhaps we don't need the "referenced by" section of the page report anymore once we report client errors on the referrer. The reason I originally added it was to find out where the links came from in case the link itself was broken.

@mthuurne
Copy link
Member Author

I went through all 4xx status codes and found the following that should be reported on the source page:

  • 400 Bad Request
  • 404 Not Found
  • 405 Method Not Allowed
  • 410 Gone
  • 414 URI Too Long

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

No branches or pull requests

1 participant