Bug 9237 - Unable to login (and no good error msg) using IE7 on 'high' privacy
: Unable to login (and no good error msg) using IE7 on 'high' privacy
Status: CLOSED FIXED
Product: MySqueezebox.com
Classification: Unclassified
Component: Player UI
: unspecified
: PC Windows XP
: -- normal (vote)
: ---
Assigned To: Andy Grundman
:
Depends on:
Blocks:
  Show dependency treegraph
 
Reported: 2008-08-20 18:04 UTC by Chris Owens
Modified: 2009-09-08 09:15 UTC (History)
1 user (show)

See Also:
Category: ---


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Chris Owens 2008-08-20 18:04:05 UTC
On boom.squeezenetwork.com, if you set IE7 to 'high' privacy settings and attempt to log in, the screen will refresh but you will be returned to the normal logged-in screen.  Instead you will be on the login screen.

Of course I don't know if there is anything that can be done about this issue.  

It was encountered by the Customer Experience team.
Comment 1 Michael Herger 2008-08-21 00:36:02 UTC
I guess the only solution will be to disable high privacy for SN (by adding the site to the whitelist). AFAIK it's disabling (some or all?) JS, Cookies etc. 

We must communicate this message to the user. But how should we do this? Any good idea?
Comment 2 Andy Grundman 2008-08-21 05:25:03 UTC
Does adding a P3P privacy header help with this issue?  I remember having to implement that on my own website a while back for some similar issue about not saving cookies or something.
Comment 3 Chris Owens 2008-08-21 10:03:29 UTC
That first comment should read "On boom.squeezenetwork.com, if you set IE7 to 'high' privacy settings and attempt to log in, the screen will refresh but you will not be moved on to the normal logged-in screen."
Comment 4 Andy Grundman 2008-08-21 12:51:42 UTC
Fixed in trunk r4358.
Comment 5 James Richardson 2008-08-27 21:21:18 UTC
Chris: Can  you verify this one is fixed please
Comment 6 Chris Owens 2008-08-28 10:43:06 UTC
I was able to successfully log in!  
Comment 7 James Richardson 2008-12-15 12:02:11 UTC
This bug has been fixed in the latest release of SqueezeNetwork!

If you are still experiencing this problem, feel free to reopen the bug with your new comments and we'll have another look.