IE7 currently incompatible with Client.Net :(

12 posts, 0 answers
  1. Shaun Peet
    Shaun Peet avatar
    571 posts
    Member since:
    Aug 2004

    Posted 05 Jun 2006 Link to this post

    I know this has nothing to do with telerik and has everything to do with IE, but just thought I'd point out that I can't login to my Client.net account using IE7 - which is really freakin' annoying.  What is also a little bit wierd is that I can login using IE7 on other sites - so perhaps it's not entirely an IE7 thing.  I'm a bit curious to know what type of authentication the telerik site uses (or if perhaps this is a server issue), etc., etc., so that I don't make the same mistake.
  2. Natalie Farah
    Admin
    Natalie Farah avatar
    170 posts

    Posted 06 Jun 2006 Link to this post

    Hello Shaun,

    If the login page just refreshes without logging you in and without displaying an error message, then this is an issue with the cookies of your browser. In order to resolve the problem please take a look at our login help (http://www.telerik.com/Default.aspx?PageId=2249). Follow the third set of instructions and you should not face the login problem anymore.

    Sincerely yours,
    Natalie Farah
    the telerik team
  3. Shaun Peet
    Shaun Peet avatar
    571 posts
    Member since:
    Aug 2004

    Posted 12 Jun 2006 Link to this post

    Alright, I've got things working and all is well logging in to the telerik site.

    Now, a related question.

    What causes this to happen?  There's way too many black boxes here (between the .NET framework, IIS, IE, etc.) and it's starting to get a little annoying.  This is now an issue for me because one of the sites that I just made won't allow an IE (6 or 7) login, but Mozilla or Netscape have no troubles whatsoever.  I don't think my client will appreciate telling all their potential registered users to go through the process of adding it as a trusted site, etc., etc., etc.

    The part that is particuarly frustrating is that I create sites all the time and this is the first time I've ever run across this cookie issue with one of my own sites.  It would be great if I could focus on creating web apps that are great - and focusing my learning on how to do that to the best of my abilities, without having to learn the intricacies of every bloody browser and how they handle/accept cookies.  Bah!

    All help from the community is appreciated on this one.
  4. Alex Norcliffe
    Alex Norcliffe avatar
    73 posts
    Member since:
    Dec 2004

    Posted 13 Jun 2006 Link to this post

    Hi Shaun

    Unfortunately it's a challenge we all face: without a cookie, the server just can't identify you from the rest of the otherwise anonymous requests coming in and so it has no idea whose Session collection to load up when you make that second page request.

    On the plus side however, it is possible to detect whether or not the browser is accepting cookies and at least let your users know the problem is at their end (and keep your clients not necessarily happier but perhaps more importantly re-educated).

    The two most useful techniques for this are to try setting a cookie on the login page and then re-read it upon postback. If it is blank, the browser does not accept 1st-party cookies. Another tip to hone-down the problem is upon postback of your login page, establish whether the Session collection is newly created - this will tell you whether or not the user has lost their session between loading the form and submitting it.

    Hope this helps in some way

    Alex
  5. Shaun Peet
    Shaun Peet avatar
    571 posts
    Member since:
    Aug 2004

    Posted 14 Jun 2006 Link to this post

    Appreciate the suggestion Alex, but I'm still having issues.  Here's why:

    I've created this ASP.NET 2.0 Web Application which uses the built-in membership system for authentication.  Our client has purchased a new web server from us which is running Windows Server 2003 Web Edition with all the default settings.  Before instalilng it we threw their web app on the server to test it; and have run into the cookie monster problem.  Internet Explorer, regardless of version; does not work.  However, Mozilla & Netscape do work just fine.

    So, just for fun, I created a virtual directory under another website that we are hosting in our own building.  This server is also running Windows Server 2003 Web Edition with all the default settings.  Internet Explorer (both 6 & 7) accept the cookie no problem and login just fine (as do Netscape and Mozilla).  So now I'm scratching my head and pulling out all my hair and screaming at the top of my lungs.

    To me, this sounds like a setting in IIS that controls just how the cookies are issued by the server; which therefore affects how / if IE accepts them.  So I'm hoping that somebody knows exactly why this is happening.  I'm not all that interested in determining whether or not the browser is accepting cookies; nor do I want to go down the road of having certain users use any extra steps to login simply because of their choice of browser.

    It's also quite strange to me that I had been using IE 6 for over a year with no issues on the telerik site; but when I switched to IE 7 then I could no longer login.  Strange, very strange.

    Again, all help is sincerly appreciated.
  6. Alex Norcliffe
    Alex Norcliffe avatar
    73 posts
    Member since:
    Dec 2004

    Posted 14 Jun 2006 Link to this post

    Hi Shaun

    I appreciate your points but ultimately whether you like it or not, at some point some users will hit your web app with cookies disabled or your web domain lying an untrusted IE zone and are you really not going to account for their scenario?

    Even if it's to find this problem, you need to isolate whether or not the browser is accepting the cookie - not ignore it as you suggest. If you are not concerned with the users 'going through extra steps because of their choice of browser', why not just rest on the laurel that it works in Mozilla? Because, i suspect, you would like it to work for everyone - and in this case you will sometimes have to do some hand holding. Imagine if Amazon didn't haven't a page helping users enable cookies!

    I appreciate it looks like a bug in the setup, but since ASP.NET is entirely in charge of the supply chain in terms of the responses back to the client I'm more inclined to believe what you describe does fit with IE7's installer tightening up the security zones - you mention that the site is working on a server 'in your building', is it perchance on your local network and therefore in IE's 'local intranet' zone because of the IP address?

    Worth checking...

    Answers to these questions and more can be established by using Fiddler which is a local proxy tool designed to allow you to analyse precisely the conversation between browser and server. I'm sure you can Google just as well as I can so I'll leave you to find the site; it's invaluable though and I would suggest you start there.

    Alex
  7. Shaun Peet
    Shaun Peet avatar
    571 posts
    Member since:
    Aug 2004

    Posted 14 Jun 2006 Link to this post

    :(

    Perhaps I'm not getting what you're suggesting.

    I've downloaded Fiddler and all it tells me (from what I see) is that the login page is trying to set the cookie.  It doesn't tell me anything beyond that - but since I don't get logged in I know it's not working.  I'm not sure what Fiddler is trying to tell me so I don't know where to go with that.

    What I do know is that identical applications running on different servers are behaving differently.  My PC (and the other 4 I've tested this on) have no problems logging into any other site other than that one application on that one server (so I know they accept cookies).  Nearly all, if not all, of my users in this geographic area - the ones that will be accessing the authenticated protion of this site once it goes live, are Windows users browsing with IE.  So my focus is to make absolutely sure that it works with IE; and I'll decide later wheter I'll need to concern myself with other browsers.

    The one thing I did notice with Fiddler is the cookie name that it was trying to set was ".ASPXAUTH" - the default.  I also noticed that telerik uses the same cookie name for their login.  So I changed the name of the cookie to ".BGC", deleted all the cookies on my machine, and tried again....but no luck.

    True that the server where the application does allow me to login is in the same building.  However, I'm using the fully qualified domain name to get to it so I'm pretty sure that IE would never know that it's in the same building or not - and therefore would not automatically trust it.  I'll go home tonight and confirm this.  If anything, the one that isn't working should be considered by IE to be trusted since I'm using a local IP; and not a domain name; to get to it.

    Incidentally, adding the IP address into the trusted sites AND adding it into the sites to "Always Allow" cookies has absolutely no effect.  Not a good thing either.
  8. Alex Norcliffe
    Alex Norcliffe avatar
    73 posts
    Member since:
    Dec 2004

    Posted 16 Jun 2006 Link to this post

    Hi Shaun

    Almost there. Fiddler will tell you the headers (or full text if need be) of both the request AND the response - so you can see first of al if the cookie is being sent out by the Login page, but also then see if the browser sends that cookie back in the next request (indeed, if you turned on ASP.NET tracing you would also be able to see the full request and cookies collection sent back to the server.

    The idea being you can isolate if the problem is with the browser.

    There is an MS KB article that I saw recently that mentions problems with HTTP authentication after you install IE 7 on Windows XP, however it was to do with Digest authentication so at a protocol level not cookies. However it sounded vaguely promising anyway; have a look in the KB?

    Alex
  9. Shaun Peet
    Shaun Peet avatar
    571 posts
    Member since:
    Aug 2004

    Posted 21 Jun 2006 Link to this post

    Alrighty, still having issues...

    Fiddler is telling me that the app is trying to set the cookie; and that the browser is not accepting the cookie.  I knew that already though :)

    What I really need to know is WHY this is happening so I can fix it.  I know that my browser (and all the other browsers I've tested this on) accept cookies on every other site I visit on the web.  It makes no sense to me that it should poo-poo this particular site.

    If anybody knows WHY this is happening and therefore whould have an idea of how to fix it, that's what I want to hear.  Thanks!
  10. Josef Rogovsky
    Josef Rogovsky avatar
    144 posts
    Member since:
    Sep 2012

    Posted 12 Jul 2006 Link to this post

    IIRC, there was a new beta of IE7 just released.

    What's the status of compatibility with Client.net?
  11. Natalie Farah
    Admin
    Natalie Farah avatar
    170 posts

    Posted 14 Jul 2006 Link to this post

    Hello Josef,

    Client.net is compatible with IE7 just as it is with other browsers. Looking back at the beginning of the thread, Shaun mentioned it is an IE7 issue, but unfortunately the login problem may occur under other browsers that support cookies. Our WebTeam is still researching the issue.

    Greetings,

    Natalie Farah
    the telerik team
  12. Shaun Peet
    Shaun Peet avatar
    571 posts
    Member since:
    Aug 2004

    Posted 14 Jul 2006 Link to this post

    Incidentally, I did find out the answer to my question as to WHY the cookie wasn't being accepted - the time on the server wasn't set properly and therefore the cookie was issued to the browser with an expiration date that had already passed.  That'll be the first thing I'd check if I encounter the same situation again.
Back to Top