views:

17

answers:

1

I have a simple ASP.Net 3.5 site that is essentially of the master/detail variety. A master page shows a GridView of database records, and clicking on Edit for a given row brings up an edit form with a DetailsView. Pretty standard stuff. Now, I have the GridView in an UpdatePanel, and launch the edit form with a jQuery FancyBox. After saving the edited record, the child page updates the parent, and briefly highlights the edited row. Lots of AJAXy goodness, and it all works perfectly...

... except when I uncheck "Anonymous access" for the site in IIS. Then, the jQuery part gets a bit squirrelly and unpredictable. Namely, the row highlighting stops working most of the time. If I go back and re-enable Anonymous access, it all works fine.

I turned off Anonymous access since I'd like to have the site know who the user is based on their Windows login. I find it quite odd that this setting would break jQuery stuff, so I'm probably just not grasping some elementary concept. Would love to hear of anyone else who has had this problem (and hopefully overcome it!).

Thanks, Chris

A: 

Does the non-Anonymous user account you're using to test the site actually have read access to all the files on the site at the file-system level? This is important -- if ACLs are not consistent, then you may be running into a situation where your browser serves you part of the content from web site successfully (or from your browser cache, which you probably didn't clear), but other parts hit up against an HTTP 403 Forbidden error. These sorts of failures may happen silently in an Ajax environment.

Make sure you're using something like Firebug on Firefox or Chrome's developer tools to see what requests you're making, and the results you're getting. Watch carefully for those 403s -- that's surely a sign of trouble.

Warren
Great idea Warren - and thanks for your reply. I started running Fiddler. And of course, now that I have it running, everything is working fine. Don't know if there's any causality there or not. To answer your question, this is all on my development machine, and so my user has access to everything. Thanks, Chris EDIT: Well, when I turned Fiddler off, the problem returned. Strange.
Chris Valdivia
That's a bit unusual. Have you confirmed this problem with multiple browsers?
Warren
Problem exists in Firefox as well - with or without Fiddler running. (FWIW - this is an internal app, and will only be running on IE.) Another weird thing is that if I add a javascript alert(...) before doing the jQuery fadeIn/fadeOut, the problem doesn't occur, regardless of Fiddler or IIS. Curiouser and curiouser.
Chris Valdivia