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

Add status code 410 to abort redner() #1097

Closed
bagr001 opened this issue Aug 28, 2023 · 4 comments
Closed

Add status code 410 to abort redner() #1097

bagr001 opened this issue Aug 28, 2023 · 4 comments
Labels
enhancement 🚀 New feature or request

Comments

@bagr001
Copy link

bagr001 commented Aug 28, 2023

Description

Hi, could you please add error code 410 to the abort redner()? Thanks.

// Render the error page
render(statusCode: 401 | 403 | 404 | 410 | 429 | 500 | 503, abortReason?: string)
@bagr001 bagr001 added the enhancement 🚀 New feature or request label Aug 28, 2023
@brillout
Copy link
Member

Could you use 404 instead? What's the (practical) difference between 404 and 410?

@bagr001
Copy link
Author

bagr001 commented Aug 28, 2023

Unfortunately not. 410 is necessary for good SEO as there is a semantic difference.

The 404 indicates, that the resource is not present at the given location, and it has probably never been (or server has no idea whether it has been).

The 410, on the other hand, indicates that resource is not present anymore, but it used to be there in the past. It's a useful hint for some clients such as search engines, spiders etc., because they can remove this resource from their indexes.

@brillout
Copy link
Member

Pre-released as 0.4.139-commit-ac52a24.

@brillout
Copy link
Member

I probably told you this already, but in case your company is up for it: https://github.com/sponsors/brillout.

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

2 participants