ianderson:Also, I am a bit confused as you state "I can reproduce your problem" and then say "You need to find a pattern where it is reproducable". It is an intermittent issue and following the steps I described it is reproducable. As VorlonShadow mentions, the logs and tracing do not provide much insight into this issue.
I meant that certain pages on your site don't appear to do this. Others do - more static pages don't seem to have a problem. I do not know enough of the code to understand this more.
Thus blank statement that it effects IIS7 and FF 3.0.6+ always are misleading. I have a site with .net and IIS7 and FF 3.0.7 and I do not get the same problems? Why is that?
We need to break the problem down into more detailed segment to work out which area is problematic. Everyone is using .NET so there may be an issue with the stack there under certain conditions.
BTW Are you using Integrated mode or are they separate?
ianderson:The idea that there is no issue between FireFox 3.0.6 and IIS7 seems a bit odd, considering that I am experiencing it, our site users are experiencing it, and other developers are experiencing it. There clearly is some issue... the question is what is the cause of the problem.
Maybe there are closely related but I am not sure they are the same if that make sense. There seems to be other elements in this too and I am trying to work out what elements are causing the problem.
For example I can very regularly reproduce the problem (in certain situations) on your site but VorlonShadow it appears very much more intermittent.
For him It seems so far that there is a delay from when the initial packet is send to the server and IIS receiving and processing it. Is that the same for you?
ianderson:Also... just to rule out any
programming or client-side issues, as both Vorlon and I have already
mentioned, the issue disappears when switching between IIS6 and IIS7. I
have run the site on an identical setup, using the exact same code, on
IIS6 and cannot produce the issue. It is specific to hosting on IIS7.
In fact, I even tried hosting on IIS7 in IIS6 classic-mode but also
experienced the issue. So I guess there is a chance that it is a
problem with the Server 2008 networking stack and FF... since IIS7 and
Server 2008 are inseparable there's no easy way to determine where the
problem lies.
That is interesting that it occurs in the IIS6 mode on Win2008. I do not know about the differences between what happens running in IIS6 mode but there must be some similarities.
But this leads me to think that it may be something to do with IIS.
Could you also tell me does it occur on the server itself? Could you install FF on there and reproduce the issue.
It *could* I suppose also be the network card on the machine maybe it is delaying something getting to the IIS.
Is there anything in the perfmon for the queue times when you have this problem? The behaviour look a little like this.
What would be useful is if you code generate a more simple pick of code, that could be tested.
Maybe just a dummy database and 1 page that causes the problem.
Sorry if I sound a little curt in the replies I am just trying to understand the issue.