R
Robert Aldwinckle
solaceinblue said:
I don't think I have misunderstood your posts.
I just did a review of them. Mostly Me too! with very little detail.
Notice that most of them then don't get any reply?
With this rant you gave us something to react to but in fact it is
in a piggyback thread to a discussion started by someone
who did provide a specific example of a problem site.
I can see why a different browser might have a different effect.
Look at the source? Browser dependent code starts it and
is scattered throughout. I'm not sure exactly what this bit does
<example>
<script type="text/javascript" language="JavaScript1.1"><!--
if (navigator.appName.indexOf("Microsoft")>=0) {
document.domain = 'gay.com';
}
//--></script>
</example>
but let's assume that a lookup for the domain name is required for it.
So, I tried that lookup in nslookup and it timed out.
If that is happening to your IE too it might explain your symptom.
In fact, you could try doing
ping -n 1 gay.com
and
ping -n 1 www.gay.com
before trying to load the page and see if that helps.
You would be doing the pings just to check that the lookups
were working but more importantly in contrast to the lookups
done by nslookup the lookups done for ping or tracert
may be cached by your DNS client which might accelerate
subsequent lookups and make HTTP GET for objects from
that domain and its server more reliable. (BTW I am only
able to know that this information applies to your case because
I bothered to look at one of your previous posts where you
alluded to your OS as being XPsp2.)
The privacy report (Alt-V,v) showed that there are other site names
involved with rendering the first page so if you see Red-X as well
you may want to try similar checks with their site names too.
If the home page is a problem it is JavaScript not Java.
In any case, what you could do to refine your symptom description
is modify your Security and Privacy settings to make them Prompt
wherever possible, then reply Yes (if desired) to each prompt.
I just tried that while offline. Evidently the page is non-cacheable;
doing a Ctrl-N after setting Work Offline and forcing Stay Offline
resulted in a Web Page Unavailable Offline warning page.
Refreshing that (blank) clone and allowing it to connect
resulted in two prompts for Active Scripting before the window
started showing anything. There was one final prompt for
ActiveX which I disallowed but by that time content was rendered
and the page was readable.
Disabling McAfee could change the timing. If the timing is marginal
that could make all the difference between continual failure and
regular success. More significantly though if McAfee (or any other
software you have) is allowed to interfere with the source it could be
making an error doing so which would make the whole page non-displayable.
HTH
Robert
---