It happens almost every time after logging out and quitting Safari - without changing IP address or network connection.
It does not happen, if Safari is kept running between the attempts.
Workaround seems to be:
1. Close the tab with this long message.
2. Empty Safari's cache (Command-Option-E)
After that new tab can be opened and login is possible again.
OS X 10.8.5, Safari 6.0.5
P.S. One more thing - I'm using HTTPS only. Maybe this has some relevance to the matter.
P.P.S. Enabling WebGL on Safari (Developer option) makes Safari crash after login.
Yes I can replicate it with HTTPS only login enabled. It might have something to do with when you logout it leaves you on 192.168.1.1/lougout.asp, and if your browser is like mine it will save state between sessions, then next time I open it I'm brought to 192.168.1.1/logout.asp, which doesn't present a problem when using HTTP, I just highlight and erase everything from the /logout.asp part, and hit enter and it brings me to a login screen. However in HTTPS it gets rather confused and didn't let me back in until I deleted the cookie for 192.168.1.1 (it might have been an old cookie, I wasn't having it save the HTTPS login credentials), exited the browser, then reopened the browser, browsed to another page, google.com or whatever, then tried
https://192.168.1.1:8443 to login again, whereupon I turned off the HTTPS force.
Really there is no benefit to use HTTPS locally to login to your own router. Reasons that you'd normally want to use HTTPS (public key CA verification, avoiding man in the middle attacks, and wanting the whole communication encrypted) are moot on a LAN. If I'm connecting via WPA the communication is encrypted, if I'm connecting via LAN, chances are that I'll know if my network is being physically hacked
. And the first two reasons to use HTTPS (CA verification and man in the middle attacks) are irrelevant on a LAN.
To protect your router from the outside turn off "admin by WAN" and turn on your firewall, and only enable the minimum amount of services (SSH, telnet, etc) that you need to, and maybe turn them off when you don't. Also minimize use of publicly open UPnP ports and DMZ zones.
Also change your root user name to something other than admin, make your admin password a non dictionary word, bare minimum 8+ characters in length, and include some non-English symbols in it (and do the same thing for your WPA key, or better yet get a super strong random p/w generated by crypto guru Steve Gibson's
free service) if you really want to fortify your LAN & WLAN. These ideas are just for starters, not to start a big network security talk, there are other good resources and
podcasts for that.
HTTPS login to your local router will not make anything safer, IMHO.