Manual assignment of 410 Gone response to missing content
I have a situation where a site has been migrated from an old V4 Umbraco implementation to a completely new V6.16 implementation. The URLTracker has been fantastically usefull in clearing up 404's from several years of content editors mindlessly renaming and moving pages to and fro, but I've now come across an issue I'm not sure how to resolve:
The URL Tracker is capturing 404s for files (mainly images) that used to exist on the old site but are either no longer part of the site or were media items that now have different ids and or file names. Some of these I have been able to create redirects for, but much of it is now historic junk that needs to be issued with 410 Gone, as it keeps getting crawled and cluttering up the URLTracker 404 list, making it hard to monitor real 404s.
As far as I can make out, URLTracker on has provision issuing 410 against content nodes that used to exist but have been deleted. Is there any way, either in the UI or by updating records in the [icUrlTracker] table to convert these trapped 404s into 410s? (URLTracker version 2.4.2)
The only way I can think of is by editing those entries directly in the database, by setting the RedirectHttpCode field to '410' and the Is404 field to 'false' / '0'.
But I'm not sure if it'll work.
I've just tried this and it sort of works... Requests for those resources do indeed get a response of 410 Gone, but the records also disappear from both the [404 Not Found View] and the [URL Tracker View] tabs. Do the 410's usually show up in the list when they are done automatically?
Ideally I'd like to see them in the URL Tracker View.
Actually, I'd like to see the HTTP code in a column on that page too, or at least an indicator (P,T,G perhaps?)
Nice to hear it works :-) It's true that those records do not appear in the UI, but I'll make sure they will in a future version. I'll also add support for custom HTTP Response codes in the UI.
Where we have captured multiple rows of 404s for a given resource, is it safe to just update them all to 410 or should I remove the duplicate records from the DB manually?
Manual assignment of 410 Gone response to missing content
I have a situation where a site has been migrated from an old V4 Umbraco implementation to a completely new V6.16 implementation. The URLTracker has been fantastically usefull in clearing up 404's from several years of content editors mindlessly renaming and moving pages to and fro, but I've now come across an issue I'm not sure how to resolve:
The URL Tracker is capturing 404s for files (mainly images) that used to exist on the old site but are either no longer part of the site or were media items that now have different ids and or file names. Some of these I have been able to create redirects for, but much of it is now historic junk that needs to be issued with 410 Gone, as it keeps getting crawled and cluttering up the URLTracker 404 list, making it hard to monitor real 404s.
As far as I can make out, URLTracker on has provision issuing 410 against content nodes that used to exist but have been deleted. Is there any way, either in the UI or by updating records in the [icUrlTracker] table to convert these trapped 404s into 410s? (URLTracker version 2.4.2)
Thanks
The only way I can think of is by editing those entries directly in the database, by setting the RedirectHttpCode field to '410' and the Is404 field to 'false' / '0'.
But I'm not sure if it'll work.
Hi,
I've just tried this and it sort of works...
Requests for those resources do indeed get a response of 410 Gone, but the records also disappear from both the [404 Not Found View] and the [URL Tracker View] tabs. Do the 410's usually show up in the list when they are done automatically?
Ideally I'd like to see them in the URL Tracker View.
Actually, I'd like to see the HTTP code in a column on that page too, or at least an indicator (P,T,G perhaps?)
Hi Gary,
Nice to hear it works :-) It's true that those records do not appear in the UI, but I'll make sure they will in a future version. I'll also add support for custom HTTP Response codes in the UI.
Thanks for this question and your thoughts!
Is it still an issue that 410's doesn't appear in the UI ?
Thanks Stefan, that would be great!
One last question Stefan...
Where we have captured multiple rows of 404s for a given resource, is it safe to just update them all to 410 or should I remove the duplicate records from the DB manually?
I'd remove the duplicates.
is working on a reply...
This forum is in read-only mode while we transition to the new forum.
You can continue this topic on the new forum by tapping the "Continue discussion" link below.