Please Log in or Create an account to join the conversation. My best guess is that a PHP script that gets triggered by the clicking the logout button is causing some kind of internal loop - possibly related to killing off a session.Īfter a quick look around the codebase (gulp!) I'm unable to see any reason for the oddity and am stumped. If I kill the browser session and then goto It looks like the Browser although successfully accessing the page (200) never actually gets it. Here’s how to tell exactly which tablet model you have. Even if you know you have a Fire, Fire HD, or Fire HDX, there are several different generations of hardware. " "Mozilla/5.0 (Windows NT 6.1 WOW64 rv:37.0) Gecko/20100101 Firefox/37.0" Amazon’s Fire Tablet, formerly known as Kindle Fire, comes in 7, 8, and 10 inch versions. Whilst stuck in the loop the Apache access_log displays the following approximately three times per second: It's as if the tech has advanced around twenty years, but our conversations around it have only advanced about ten. Xerte Toolkit Version: 2.1 (git git-103-gebc6f34) 90 to download pages and sites which take a long time. This kills the browser and also Apache which runs out of resources. My computer isn't slow except when I'm connected to the net with Firefox 37.0.1 or Chrome. Instead the browser gets stuck in an unending loop calling the home page but never seeming to get it or display it. When a user clicks the logout button they are not being returned to the home page.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |