On Thu, Jul 14, 2016 at 3:11 PM, Jose Antonio Senna <jasse...@vivointernetdiscada.com.br> wrote: > On July 13 dmccunney said: > > > The issue here may be the ancient FF version. > > Sites tend to use browser identification code > > that will complain if it thinks you > > are running an unsupported browser that can't > > render the site. > > FF 2.X has been unsupported for years. > > This may explain why the Sourceforge server failed to > detect javascript capability in my browser, but it is no > reason for the "disaster recovery mode" message. > Anyway, Sourceforge is now working again, and their > "Site Status" page acknowledges they had a problem. > [...] > I think it is more likely they use jquery to make the > client return a response dependent on the javascript > version it supports.
Yes, I think you are correct that they probably use js in their error page, and they are detecting the version of js supported. But as you say, SourceForge has fixed their server problem, so I think this issue is moot. Jim ------------------------------------------------------------------------------ What NetFlow Analyzer can do for you? Monitors network bandwidth and traffic patterns at an interface-level. Reveals which users, apps, and protocols are consuming the most bandwidth. Provides multi-vendor support for NetFlow, J-Flow, sFlow and other flows. Make informed decisions using capacity planning reports.http://sdm.link/zohodev2dev _______________________________________________ Freedos-user mailing list Freedos-user@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/freedos-user
