You should have both, since both are valid (error state) outcomes from a request. Is the client saying that all “URL missing” type errors must result in a 410 (Gone permanently, never coming back) rather than a 404 (Gone, but may return at some point)? How are you going to determine which of these outcomes to signal?
Walter
On Sep 16, 2013, at 1:09 PM, BigG wrote:
I have been asked to remove my 404.shtml page and set up a 410 one instead.
Is this just a case of creating a 410.shtml page or is there something extra I have to do server-side?
Lists all of the status codes in one place, for easy perusal. If a status has a Rails-specific “short code”, that’s listed in the details as well.
Walter
On Sep 16, 2013, at 1:15 PM, Walter Lee Davis wrote:
You should have both, since both are valid (error state) outcomes from a request. Is the client saying that all “URL missing” type errors must result in a 410 (Gone permanently, never coming back) rather than a 404 (Gone, but may return at some point)? How are you going to determine which of these outcomes to signal?
Walter
On Sep 16, 2013, at 1:09 PM, BigG wrote:
I have been asked to remove my 404.shtml page and set up a 410 one instead.
Is this just a case of creating a 410.shtml page or is there something extra I have to do server-side?
Hmmm. The Apache rewrite page said that the [G] flag would signal Gone, and they also said it would send a 410 status. See what happens if you remove both of the ErrorDocument directives. (Just put a # in front of each line and save the file.)
Then also see what happens if you add a L (last rule, stop processing) to the flags, as [G,L].
Other things to check here: the .htaccess is in the folder just outside of where the /forum/ folder used to be, correct? What happens if you remove either the ^ or the / or both from the match string?
Walter
On Sep 17, 2013, at 1:36 AM, BigG wrote:
I have deleted the folder ‘forum’.
Have added this to the .htaccess file (the error doc references were already in there: