>Ok, we had it again. This time, we tracked more information.
>
>When that bug happened, it was returned by one WWC server only. As I previously mentioned, when that happens, for that particular WWC server, it does not even go in the WWC VFP server. The garbage incoming header is returned back to the browser at the DLL level. However, when we go in WWC admin page, we see that all hits are recorded to the WWC server. I mean for all WWC servers. So, the one bugging is also recording the hit. So, this means, it goes at least somewhere at the WWC level. However, the cumulative hit for that one does not log, or at least, after 10 minutes, it only moved from 4 to 5 cumulative hits where all the other 3 servers moved from dozens of hits within the same lap time.
>
>So, again, we request all help we can get about that one. We are also tired of that bug.

And, for those who were wondering what transaction was last done, here is the info. We can't tell if that was the same scenario for all the other situations as this is only the first time we have established that tracking to that level. The transaction was the auto refresh from the left frame to update the IDs. When we send that, we send that line at first to send in the browser's memory an auto refresh for the next interval.

'< META HTTP-EQUIV=Refresh CONTENT='+ALLTRIM(STR(MEMBER.MENUREFRES))+'>'

That transaction is executed thousands of time per day. Why would that transaction cause that behavior at a specific interval?

We have other data after that line. However, that is the start of the string we send back to the Response.Write().