On Fri, Aug 29, 2014 at 4:44 PM, Gregg Eshelman <[email protected]> wrote:

> On 8/29/2014 4:02 AM, Mark Wendt wrote:
> > On Fri, Aug 29, 2014 at 5:53 AM, Erik Christiansen <
> [email protected]>
> > wrote:
> >
> >> On 29.08.14 05:23, Mark Wendt wrote:
> >>>> On 28 August 2014 17:32, David Armstrong <[email protected]> wrote:
> >>>>> http://linuxcnc.org/docs/html/examples/spindle.html
> >>
> >>> Hmmm, our web site doesn't seem to be responding this morning.  I can
> >> ping
> >>> the server, but Firefox sits there spinning it's wheels.  Can anyone
> else
> >>> get to the web site?
>
> Whenever Firefox has a problem with a site, first try Internet Explorer
> or Google Chrome. If those don't have a problem with the site, it's
> Firefox with the problem.
>
> If all three browsers exhibit the same issue then it's a problem with
> the site or your internet connection.
>
> The people who do Firefox apparently have a bit of "institutional
> memory" about how they do certain parts of web browser code, which they
> keep repeating despite having started over "completely clean" several
> times with Netscape, then Firefox.
>
> Starting around Netscape 3.0 they got something *wrong* in it with how
> to handle forms where it'd just sit there doing nothing then falsely
> claim "Document Contains no Data". Meanwhile Internet Explorer on the
> same site, same time, same computer would submit the form with out a
> problem.
>
> Eventually Netscape got better at that but never fully fixed. At some
> point they removed the "error" message so it'd just silently fail.
> Netscape 4.x, 6.x (5.x was a "clean start" they abandoned and never
> released) and all the way up to 9.x had the same problem in some degree.
>
> Firefox still has that problem with some sites where it'll sit there
> doing nothing for a while then give up.
>
> Would be nice if they'd just decide to root out what part of their code
> is responsible for that problem, figure out a fix, then make the
> error(s) a part of their "programming bible" with a large DO NOT EVER DO
> THIS BECAUSE IT'S BUGGY! note.
>


Gregg,

Yep, did that too.  Didn't load on Chrome either.  I'm a Unix/Linux
Sysadmin at work.  I will never have Internut Exploder running on any
desktop or server I manage, and have managed to keep the "Virus That
Masquerades As An Operating System" TM off any system under my kind
ministrations.  It was a problem neither in the browser or the web site.
We tracked it down to an IPv6 routing issue between my desktop and the web
server.  I had issues getting to other servers vi IPv6 that routed through
the same link.  It cleared up in about 15 minutes or so.

Mark
------------------------------------------------------------------------------
Slashdot TV.  
Video for Nerds.  Stuff that matters.
http://tv.slashdot.org/
_______________________________________________
Emc-users mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/emc-users

Reply via email to