Howdy Brett, Art & @earlyimp:
Brett, I popped in for a little testing on a stock BTO location, and confirmed that this behavior has nothing to do with your using URL rewriting to mask the /productcart/pc/ directories. The behavior is the same with or without that URL rewriting in the mix.
I think you've rather nailed it in observing that this only happens on BTO products set to skip the product page and go straight to the configuration page. The explanation by @earlyimp doesn't in any way explain why this behavior on only these pages and not all "SEO URLs" bouncing off of IIS's custom 404 handling, though it explains some of what is going on behind the scenes here: The ".htm" URL is fictitious, it doesn't exist. IIS detects this as a 404 error, but is set to handle this event by executing /productcart/pc/404.asp. That script parses things out from the query string generated (?404;http://www.liftchair.com:80/store/pc/wall-hugger-lift-chair-w-memory-foam-seat-p763.htm) and having detected from this sting that the page is a product page, it transfers execution to viewprd.asp while returning a 200 status (so, on the client side everything should look just dandy when IIS and this script render the page). Same thing for category and content pages.
What's different on BTO configuration pages set this way is that viewprd.asp detects the "skip details page" setting and transfers again to configureprd.asp. I'm not smart enough to completely get the difference, but clearly the double server.tranfer is what is different, so it's reasonable to assume that's what's causing this behavior in Firefox (or maybe what is revealing "the man behind the curtain" in what is actually happening here) while not on any other pages "bouncing off of" 404.asp.
Given that the behavior is only exhibited on a refresh, I'm not sure whether it's worth getting worked up about from an SEO perspective. However, it would seem that if one really wanted to avoid this, the "skip details" setting could be detected in 404.asp and the server.transfer could be directed immediately to configureprd.asp there rather than first transferring to viewprd.asp and then transfering again to configureprd.asp (as this all happening inside IIS at this point, I'm still puzzling over how Firefox detects this).
As a quick test, I edited 404.asp to transfer directly to configureprd.asp rather than viewprd.asp while hitting a page set this way, and see that there is more to sort out as the product ID got lost that way (though a quick search of why left me wondering why). Anyways, it would take some more investigation/work to handle it that way, but I'm really not sure it would be worth the time/effort unless there's a good SEO reason for it.
Art: I'm curious in what context you've seen this on your site, as I wasn't aware that you were using BTO and it appears to me to only be an issue with BTO products set to skip the details page.
|