noncarborundum
Posts: 320
Joined: Jan. 2009
|
| Quote (midwifetoad @ Sep. 24 2011,14:08) | My guess as a minor league web programmer is that IE and FireFox "fix" the URL sufficiently to get to the main page, but fail when moving down to the specific post.
It could be the UD software doing this, but why would it be different on different browsers, unless it is the browser doing it?
Unless I misread you, it only happens when the URL is defective, so regardless of the symptom, the cause is a defective URL. |
I've only seen it happen on that specific page, and it still happens even if I edit the URL to remove the comment tag from the end. In fact, it even happens when I go to UD's front page and follow the link from there. Really. It's not AtBC's URL mangling that's at fault here.
I've followed dozens of badly formatted links from AtBC to UD. I know how to repair these links so that they work. I've never seen this particular symptom before.
I notice that when I try to load that page, regardless of browser, it spends quite a long line displaying the spinning in-progress indicator on the title tab and claims to be waiting to read something from googlesyndication.com. The difference between browsers seems to come down to what happens when the wait times out. Firefox and IE treat it as a "reset connection" error, while Chrome just to gives up trying, leaving the page displayed but not completely loaded (even Chrome doesn't display the entire page, as judged by what shows up when you "view page source").
--------------
"The . . . um . . . okay, I was genetically selected for blue eyes. I know there are brown eyes, because I've observed them, but I can't do it. Okay? So . . . um . . . coz that's real genetic selection, not the nonsense Giberson and the others are talking about." - DO'L
|
