Join GitHub today
GitHub is home to over 36 million developers working together to host and review code, manage projects, and build software together.Sign up
[bug report] Login issues on 1.2.17rc1 with IE11 and Android Browser #1544
What were you doing?
I have updated from version 1.2.16 to 1.2.17rc1.
What were you doing?
I have done an update via the web interface.
What did you expect to happen?
The login should have worked.
What happened instead?
It works only with Firefox (49.0.1), not with IE (11.0.9600.18349) and also not on Android Smartphone / Tablet. Only Firefox reacts when the login button is pressed, the other browser does not.
Branch & Commit or version of OctoPrint
Before the update 1.2.16.
Printer model & used firmware incl. Version
Printer: Vellemann Vertex K8400 (electronics replaced by Ramps 1.4).
Browser and Version of Browser, Operating System running Browser
Windows 7 Pro 64Bit / Android
Link to octoprint.log
link to contents of terminal tab or serial.log
Screenshot (s) showing the problem:
It looks like there is some information missing from your bug report that will be needed in order to solve the problem. Read the Contribution Guidelines which will provide you with a template to fill out here so that your bug report is ready to be investigated (I promise I'll go away then too!).
If you did not intend to report a bug but wanted to request a feature or brain storm about some kind of development, please take special note of the title format to use as described in the Contribution Guidelines.
Also make sure you are at the right place - this is the bug tracker of the official version of OctoPrint, not the Raspberry Pi image OctoPi nor any unbundled third party OctoPrint plugins or unofficial versions. Make sure too that you have read through the Frequently Asked Questions and searched the existing tickets for your problem - try multiple search terms please.
I'm marking this one now as needing some more information. Please understand that if you do not provide that information within the next two weeks (until 2016-10-26 23:00 UTC) I'll close this ticket so it doesn't clutter the bug tracker. This is nothing personal, so please just be considerate and help the maintainers solve this problem quickly by following the guidelines linked above. Remember, the less time the devs have to spend running after information on tickets, the more time they have to actually solve problems and add awesome new features. Thank you!
PS: I'm just an automated script, not a human being, so don't expect any replies from me :) Your ticket is read by humans too, I'm just not one of them.
referenced this issue
Oct 13, 2016
Just tested on IE myself: 11.633.10586.0. Login worked perfectly fine. Don't have an Android device on hand ancient enough that it still doesn't ship with Chrome as browser by default, so couldn't cross check there personally.
The only change between 1.2.16 and 1.2.17rc1 even remotely related to login behaviour was making sure to on logout also delete the old