Comments on: logging 404 errors on your site and generating traffic from it http://www.digimantra.com/tutorials/logging-404-errors-on-your-site-and-generating-traffic-from-it/ Technology tips for all Thu, 29 Jul 2010 06:37:51 +0000 hourly 1 http://wordpress.org/?v=3.0 By: Sachin Khosla http://www.digimantra.com/tutorials/logging-404-errors-on-your-site-and-generating-traffic-from-it/#comment-10305 Sachin Khosla Tue, 10 Nov 2009 06:29:17 +0000 http://www.digimantra.com/?p=660#comment-10305 Its URI and its the part after your domain example http://digimantra.com/any_part_after_this_is_URI Its URI and its the part after your domain example
http://digimantra.com/any_part_after_this_is_URI

]]> By: Alap http://www.digimantra.com/tutorials/logging-404-errors-on-your-site-and-generating-traffic-from-it/#comment-10304 Alap Tue, 10 Nov 2009 06:08:16 +0000 http://www.digimantra.com/?p=660#comment-10304 I am not a Programming guy. There's a typo in the Point 2? "magical file which handles the bad URI" It should be URL right?? It's the Exceptions that prove the rule right??!! I am not a Programming guy.

There’s a typo in the Point 2?
“magical file which handles the bad URI”
It should be URL right??

It’s the Exceptions that prove the rule right??!!

]]> By: Raph http://www.digimantra.com/tutorials/logging-404-errors-on-your-site-and-generating-traffic-from-it/#comment-1735 Raph Thu, 18 Jun 2009 05:44:52 +0000 http://www.digimantra.com/?p=660#comment-1735 ... If I would cache them, I’d use a database, not a file, unless I’m expecting a sh..load of logs ... I misplaced that... should be after "... and process them to readable data." … If I would cache them, I’d use a database, not a file, unless I’m expecting a sh..load of logs …

I misplaced that… should be after “… and process them to readable data.”

]]> By: Raph http://www.digimantra.com/tutorials/logging-404-errors-on-your-site-and-generating-traffic-from-it/#comment-1734 Raph Thu, 18 Jun 2009 05:42:38 +0000 http://www.digimantra.com/?p=660#comment-1734 I would agree with Leafnode. You could just write a script that pulls all 404's from a specific date and process them to readable data. Regarding your script: although all open resources (except persistent connections) will be closed at script end, I'd recommend close the file stream through fclose($fH). If I would cache them, I'd use a database, not a file, unless I'm expecting a sh..load of logs. header("Location:http://www.mydomainname.com/?s=$fail_query"); //will never go beyond this You can't be sure of that. If you want the script to end there, always use 'exit' (or die(), which of course is an alias of exit). I would agree with Leafnode. You could just write a script that pulls all 404′s from a specific date and process them to readable data.

Regarding your script: although all open resources (except persistent connections) will be closed at script end, I’d recommend close the file stream through fclose($fH). If I would cache them, I’d use a database, not a file, unless I’m expecting a sh..load of logs.

header(“Location:http://www.mydomainname.com/?s=$fail_query”);
//will never go beyond this

You can’t be sure of that. If you want the script to end there, always use ‘exit’ (or die(), which of course is an alias of exit).

]]> By: Daily Digest for June 16th | Squirrel Hacker http://www.digimantra.com/tutorials/logging-404-errors-on-your-site-and-generating-traffic-from-it/#comment-1718 Daily Digest for June 16th | Squirrel Hacker Tue, 16 Jun 2009 23:22:59 +0000 http://www.digimantra.com/?p=660#comment-1718 [...] logging 404 errors on your site and generating traffic from it | DigiMantra — 11:31am via [...] [...] logging 404 errors on your site and generating traffic from it | DigiMantra — 11:31am via [...]

]]> By: Leafnode http://www.digimantra.com/tutorials/logging-404-errors-on-your-site-and-generating-traffic-from-it/#comment-1713 Leafnode Tue, 16 Jun 2009 06:45:52 +0000 http://www.digimantra.com/?p=660#comment-1713 I'd like to note that all 404 errors are logged by webserver - in case of Apache it's errorlog file for given virtual server. I know that it's not the case here, but sometimes, when URLs are being constructed dynamically via RewriteEngine, sometimes people forget to send 404 code for non-existant pages, which breaks many things, for instance automated link checking, bookmark verification etc. I’d like to note that all 404 errors are logged by webserver – in case of Apache it’s errorlog file for given virtual server.

I know that it’s not the case here, but sometimes, when URLs are being constructed dynamically via RewriteEngine, sometimes people forget to send 404 code for non-existant pages, which breaks many things, for instance automated link checking, bookmark verification etc.

]]>