Last post Mar 03, 2011 08:20 AM by jimijani1982
Feb 24, 2011 12:02 AM|jimijani1982|LINK
i have an asp.net app , when i browse it with firefox , it gives an abnormal behavior . for each request ( get/response) an aborted response is processed(not recieved) by the firefox client and than the
get request is sent once again and contents are refetched .
any idea why is this happening .
1. i took the readings using fiddler
2. I am not doing any heavy opertion any where in the whole app
Feb 24, 2011 11:54 PM|stiletto|LINK
Could you be observing a credential exchange transition?
I know I've seen multiple requests on IE where it tries multiple sets of cached credentials. I most often see this right after I've changed my network password until IE gets convinced that the current credentials are sufficient.
Feb 25, 2011 01:59 PM|jimijani1982|LINK
yes , i am logging into the application.
Feb 26, 2011 12:42 AM|stiletto|LINK
What kind of Authentication mode is your app running under? If you're using FormsAuthentication, trace the headers and see if the Authentication cookie is being sent with the first request.
Feb 26, 2011 06:23 PM|jimijani1982|LINK
no i am using my own authentication i.e on succesful login , at server, a variable in session object is saved that keeps track if user has logged in or not.
Feb 26, 2011 06:32 PM|raju dasa|LINK
may be Fiddler is causing the problem!
Mark as Answer if it helps.
Feb 26, 2011 07:28 PM|jimijani1982|LINK
no , application is not getting logged in ... as i said , every request is getting aborted and a get request is issued immediatly after it .
Feb 28, 2011 02:18 AM|stiletto|LINK
In that case verify that the Session cookie is being passed on the first request.
Mar 01, 2011 05:10 AM|jimijani1982|LINK
the first request(post) is not even sent to the server , firefox aborts it itself . and than send a get request to that page.
Mar 01, 2011 09:52 PM|stiletto|LINK
What does the form tag look like in the rendered HTML that should be triggering the POST?
Mar 03, 2011 08:20 AM|jimijani1982|LINK
yes , its post.
the problem is surely somewhere in the browser because it working fine with all other browsers (crome , IE).
when i debugged the application , the submit handler never hit as i said it got aborted at the client end ( for what reason i dont know ).