A message from our CEO about the future of Stack Overflow and Stack Exchange. Read now.
2 410 not 401
source | link

I'm going to answer this from the perspective of a webmaster who is familiar with the error codes that your web app should produce.

A 404 Not found error is a very general error for the case when a URL was entered that cannot be parsed. You may not know what area of the site the user was looking for. There may even be nonsense in the URL like /xyszes/thau. Were they looking for a meeting? Who knows. At the very least you need some generic 404 page for the case in which your server can't make heads or tails of the URL.

A 401410 Gone is a page that I often customize for different content types. When you remove a meeting, you should return a 410 status with a custom message like This meeting was yesterday, click here to schedule a new meeting.

For URLs that are almost correct, you should use a 301 Moved Permanantly status to take the user directly to the correct page. You might want to take advantage of modules like mod_speling (sic) that can correct misspelled URLs. You should also implement redirects manually for pages or sections of your website that have actually moved to a new URL. I find it useful to implement a custom 404 script that tries the words from the URL in site search and then redirects to the first result if there is one.

I'm going to answer this from the perspective of a webmaster who is familiar with the error codes that your web app should produce.

A 404 Not found error is a very general error for the case when a URL was entered that cannot be parsed. You may not know what area of the site the user was looking for. There may even be nonsense in the URL like /xyszes/thau. Were they looking for a meeting? Who knows. At the very least you need some generic 404 page for the case in which your server can't make heads or tails of the URL.

A 401 Gone is a page that I often customize for different content types. When you remove a meeting, you should return a 410 status with a custom message like This meeting was yesterday, click here to schedule a new meeting.

For URLs that are almost correct, you should use a 301 Moved Permanantly status to take the user directly to the correct page. You might want to take advantage of modules like mod_speling (sic) that can correct misspelled URLs. You should also implement redirects manually for pages or sections of your website that have actually moved to a new URL. I find it useful to implement a custom 404 script that tries the words from the URL in site search and then redirects to the first result if there is one.

I'm going to answer this from the perspective of a webmaster who is familiar with the error codes that your web app should produce.

A 404 Not found error is a very general error for the case when a URL was entered that cannot be parsed. You may not know what area of the site the user was looking for. There may even be nonsense in the URL like /xyszes/thau. Were they looking for a meeting? Who knows. At the very least you need some generic 404 page for the case in which your server can't make heads or tails of the URL.

A 410 Gone is a page that I often customize for different content types. When you remove a meeting, you should return a 410 status with a custom message like This meeting was yesterday, click here to schedule a new meeting.

For URLs that are almost correct, you should use a 301 Moved Permanantly status to take the user directly to the correct page. You might want to take advantage of modules like mod_speling (sic) that can correct misspelled URLs. You should also implement redirects manually for pages or sections of your website that have actually moved to a new URL. I find it useful to implement a custom 404 script that tries the words from the URL in site search and then redirects to the first result if there is one.

1
source | link

I'm going to answer this from the perspective of a webmaster who is familiar with the error codes that your web app should produce.

A 404 Not found error is a very general error for the case when a URL was entered that cannot be parsed. You may not know what area of the site the user was looking for. There may even be nonsense in the URL like /xyszes/thau. Were they looking for a meeting? Who knows. At the very least you need some generic 404 page for the case in which your server can't make heads or tails of the URL.

A 401 Gone is a page that I often customize for different content types. When you remove a meeting, you should return a 410 status with a custom message like This meeting was yesterday, click here to schedule a new meeting.

For URLs that are almost correct, you should use a 301 Moved Permanantly status to take the user directly to the correct page. You might want to take advantage of modules like mod_speling (sic) that can correct misspelled URLs. You should also implement redirects manually for pages or sections of your website that have actually moved to a new URL. I find it useful to implement a custom 404 script that tries the words from the URL in site search and then redirects to the first result if there is one.