Not looking for all functionality, just some core functionality (at least read content). I recognize nothing can be supported forever, especially when not in the scope of testing, but when it’s reported and if it’s an obvious fix that does not significantly impact operability, consider such. I would ask Discourse team review what changes were made and if there is a way to mitigate this breaking change. Interestingly, I fired up a WINXP PC running FF 52.9.0 ESR and notwithstanding the banner “your browser is too old to work in this site”, the site appeared to load fine, so it seems rather specific/esoteric. They broke and fixed it once before in December and we sincerely hope they can revert that change and restore that functionality. At least it’s not something malicious where I’ve got to worry about being hacked. Curious why such a device would have a web server on it or even have open ports. Brute Force Vulnerability in Apreliums Abyss Web Server. I reported this on the Jenkins site and the admin has indicated this is likely, " because replaceAll is not available in Firefox 68." and provided evidence from Saucelabs at about 00:17 sec mark the error message.Įarlier this month a JavaScript change broke StackOverflow functionality (link below) for the second time on the StackOverflow/Exchange sites. Abyss Web Server version 1.0.3 shows file and directory content. “View Source” spins off to an abyss of nothingness. The page appears to fetch data for a few seconds, then blankness. Never been here before, but it doe snot load either. That is also evidently the core for other browsers like Waterfox, Silk browser on FireStick. Meta tag in the header/source says Discourse 2.9.0.beta2Īt some between Monday and Wednesday this week (/16), the site no longer loads on legacy Android Firefox browsers. The remote web management interface of Aprelium Technologies Abyss Web Server 1.1. I am a user of community(dot)jenkins(dot)io (sorry can only post 2 links) which according to one of the admins, uses a Discourse instance sponsored by the official discourse group.
0 Comments
Leave a Reply. |