Ds:irm

[Stecyk]

Hi,

I am curious about DS:IRM. Up until a month or two ago, I never saw this in my server logs. Now it is fairly common.

This server entry below is me. But I never, ever use my blog.speciousargument.com url. Rather, I always use speciousargument.com/blog/. All my bookmarks, everything, are set to my "normal" way. I can even view my address bar in Firefox and my server log.

68.xxx.xx.71 - - [17/Feb/2007:23:25:50 -0500] "GET /|DS:IRM:blog.speciousargument.com|//blog/ HTTP/1.1" 200 125670 "-" "Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.8.1.1) Gecko/20061204 Firefox/2.0.0.1"

I have also noticed that FeedBurner hits the DS:IRM thingy too. But FeedBurner is preprogrammed to fetch a file using the normal url without the DS:IRM thingy. The same applies to other services such as Newsgator etc.

So I am curious why I am seeing this DS:IRM thingy throughout the server logs. Any explanations? And how do I make it go back to the way it was?

Best regards,
Kevin

[Joseph]

This is a new way of parsing the logs that we have implemented to allow you to see how many hits your various add-on domains are receiving. Please see this topic for more information: Click here (http://www.aota.net/forums/showthread.php?t=19173)

For a way to disable this feature, please view Terra's post below.

[Stecyk]

Joseph,

As I understand the link you provided, my server log should be telling me that the incoming link didn't come from its usual path (www.speciousargument.com/blog/) but rather (www.blog.speciousargument.com/)?

At least then, you would be able to differentiate within your web statistics based on request pathing...

Ah, nooo. I am getting wrong information.

I know which address I use. I also know which address I have given FeedBurner to grab my feed. I also know that others who access my feed have not suddenly switched en masse. When they grab the feed from my weblog, they grab the "traditional" path. Until now, only FQ and myself were even aware of my IROs or IRMs.

If I misunderstood the thrust of that link, please enlighten me.

Regards,
Kevin

[Stecyk]

Here's an example:

62.47.21.xxx - - [18/Feb/2007:07:52:21 -0500] "GET /|DS:IRM:blog.speciousargument.com|//blog/archives/2006/07/bike_riding_stoney_trail_bridge.php HTTP/1.1" 200 33256 "http://at.search.yahoo.com/search?p=stoney+bike&ei=UTF-8&fr=sfp&x=wrt&meta=vc%3D" "Mozilla/4.0 (compatible; MSIE 6.0; Windows 98; .NET CLR 1.1.4322)"
62.47.21.xxx - - [18/Feb/2007:07:52:22 -0500] "GET /|DS:IRM:blog.speciousargument.com|//blog/mt-site.js HTTP/1.1" 200 4402 "http://www.speciousargument.com/blog/archives/2006/07/bike_riding_stoney_trail_bridge.php" "Mozilla/4.0 (compatible; MSIE 6.0; Windows 98; .NET CLR 1.1.4322)"
62.47.21.xxx - - [18/Feb/2007:07:52:22 -0500] "GET /|DS:IRM:blog.speciousargument.com|//blog/styles-site.css HTTP/1.1" 200 22603 "http://www.speciousargument.com/blog/archives/2006/07/bike_riding_stoney_trail_bridge.php" "Mozilla/4.0 (compatible; MSIE 6.0; Windows 98; .NET CLR 1.1.4322)"
62.47.21.xxx - - [18/Feb/2007:07:52:23 -0500] "GET /mt334/mt-static/simages/img_136.gif HTTP/1.1" 200 229 "http://www.speciousargument.com/blog/archives/2006/07/bike_riding_stoney_trail_bridge.php" "Mozilla/4.0 (compatible; MSIE 6.0; Windows 98; .NET CLR 1.1.4322)"

Note that it came from a Yahoo search. So let's look at that Yahoo search using the string provided in the server log, namely:

http://at.search.yahoo.com/search?p=stoney+bike&ei=UTF-8&fr=sfp&x=wrt&meta=vc%3D

http://i69.photobucket.com/albums/i76/KStecyk/fqyahoo.png

Looks like the traditional path to me.

I look forward to your explanation. Maybe I am missing something obvious?

Regards,
Kevin

[Terra]

This is indeed an error in the new IRx_tagged_logging subsystem... I am currently investigating a couple different ways of resolving this condition...

Any explanations? And how do I make it go back to the way it was?
In the interim, please view the following directives that control this new FutureQuest subsystem...
http://www.aota.net/forums/showthread.php?postid=130329#post130329

In short, add the following to a .htaccess file in your blog subdirectory:
FQ_tagged_logging_irx off

--
Terra
sysAdmin
FutureQuest

[Stecyk]

This is indeed an error in the new IRx_tagged_logging subsystem... I am currently investigating a couple different ways of resolving this condition...

Thank you Terra. Given that you're addressing this issue, I will simply wait for you to fix it. I don't do anything with the data other than look at it occasionally. I was puzzled why I was getting the IRx's when nobody knew they existed. I might get some now when this thread is Googled.

In summary, I will just wait for your fix.

Thank you for replying promptly. :smile:

Best regards,
Kevin

[Terra]

Kevin, the IRX Tagging problem has been fixed, please view:
http://www.aota.net/forums/showthread.php?p=159490

[Stecyk]

Thank you! :yeah: