Errors & Bugs to Fix
- Thread starter Admin
- Start date
Great info!A lot of them would hard to find without your help.
I've merged them all.
Thx Loso!!
Well, some of them......I would have eventually gotten to the ones, that are Nubiles Models as well. Anyways, thanks again Loso.
There is a Problem....
There is a Problem....
with your Programming of your Index Site as it takes out all my FireFox Windows I have running. Below is the URL that is left when it takes out all my Windows of FireFox. I hope you can fix this soon, because I have NOT been on your Main Index Page for very long when it happened.
http://www.modelindexxx.com/?wicket...wicket.markup.html.pages.PageExpiredErrorPage
It happened again this time URL is this:
http://www.modelindexxx.com/?wicket:bookmarkablePage=:org.apache.wicket.mark
There is a Problem....
with your Programming of your Index Site as it takes out all my FireFox Windows I have running. Below is the URL that is left when it takes out all my Windows of FireFox. I hope you can fix this soon, because I have NOT been on your Main Index Page for very long when it happened.
http://www.modelindexxx.com/?wicket...wicket.markup.html.pages.PageExpiredErrorPage
It happened again this time URL is this:
http://www.modelindexxx.com/?wicket:bookmarkablePage=:org.apache.wicket.mark
Last edited:
Could be caused by a server reboot that I did around that time.
This is what might have happened:
1) You opened a page
2) A HTTP session is started automatically
3) Server reboot
4) after 25 minutes after the page load in step 1, the page will automatically perform a client-sided ajax call in order to keep the HTTP session alive. But because the server was rebooted, the session didn't exist anymore, and thus the error pages were shown.
The same thing can happen when a PC is put on stand-by while keeping the page in the browser.
So if it was caused by the reboot, than it shouldn't happen much. Stateless pages would prevent this problem, but with the cost of spam.
This is what might have happened:
1) You opened a page
2) A HTTP session is started automatically
3) Server reboot
4) after 25 minutes after the page load in step 1, the page will automatically perform a client-sided ajax call in order to keep the HTTP session alive. But because the server was rebooted, the session didn't exist anymore, and thus the error pages were shown.
The same thing can happen when a PC is put on stand-by while keeping the page in the browser.
So if it was caused by the reboot, than it shouldn't happen much. Stateless pages would prevent this problem, but with the cost of spam.
This is happening just being here:
http://www.modelindexxx.com/
Actually, just being on your very First Page, since your re-programming of the Time-out, in my opinion made it worse. I constantly have your Model Index up on a Tab, your BabeID Forum on a tab, and that List of Nubiles Models you made on a tab in one of my 14 Firefox Windows I have running and am using it often enough I feel to keep it from timing-out. Your Model Index Site is the only one, that times-out of all the other Model Index Sites I use for my Research and make Contributions to as well.
Rebooting your Server could explain the second URL I put up in my prior Post and the reason why it your Site took down all my other FireFox Windows in such a very short time (just five minutes or less apart).