Last modified: 2013-10-07 09:06:03 UTC

Wikimedia Bugzilla is closed!

Wikimedia migrated from Bugzilla to Phabricator. Bug reports are handled in Wikimedia Phabricator.
This static website is read-only and for historical purposes. It is not possible to log in and except for displaying bug reports and their history, links might be broken. See T56966, the corresponding Phabricator task for complete and up-to-date bug report information.
Bug 54966 - Auto-logout after 30 seconds in IE10
Auto-logout after 30 seconds in IE10
Status: RESOLVED FIXED
Product: MediaWiki
Classification: Unclassified
User login and signup (Other open bugs)
1.22.0
PC Windows 8
: Unprioritized major (vote)
: ---
Assigned To: Nobody - You can work on this!
:
Depends on:
Blocks:
  Show dependency treegraph
 
Reported: 2013-10-04 11:13 UTC by Paine Ellsworth
Modified: 2013-10-07 09:06 UTC (History)
2 users (show)

See Also:
Web browser: Internet Explorer
Mobile Platform: ---
Assignee Huggle Beta Tester: ---


Attachments

Description Paine Ellsworth 2013-10-04 11:13:08 UTC
Internet Explorer v.10:

It seems nobody at the pump can help, so here we are.  Yesterday on first login I was told to change my password, which I did.  Then I logged in and after a few seconds was automatically logged out again.  Doesn't happen in Firefox, unsurprisingly.  Either bug 54626 has not deployed yet (because I am still logged into the HTTPS), or it has deployed and this is the result, or something else - I'm no expert.  Please save the ms-bashing, since as far as I'm concerned, IE buries its competition.  ''Joys!''
Comment 1 Sam Reed (reedy) 2013-10-04 18:00:50 UTC
Usual starting place would be to clear any cache, temporary files and cookies etc - you've admitted it doesn't happen in Firefox, which means that the code what was deployed isn't completely broken.
Comment 2 Paine Ellsworth 2013-10-04 22:54:46 UTC
(In reply to comment #1)
> Usual starting place would be to clear any cache, temporary files and cookies
> etc - you've admitted it doesn't happen in Firefox, which means that the code
> what was deployed isn't completely broken.

Actually, I'd done everything I could think of.  Even lowered priv and sec to lowest possible settings.  Then I did a clear-cache in Firefox and go figure - seems to be better now, although why clearing the field in one browser helps a different browser is about a seven on my weird wicco-meter.  I'll run some more tests, and if everything's okay, I'll go ahead and shut this down.  Thank you, btw!
Comment 3 Paine Ellsworth 2013-10-07 09:06:03 UTC
It seems to be okay, now.  Sorry to be a bother.  Joys to all!

Note You need to log in before you can comment on or make changes to this bug.


Navigation
Links