* cleared my browser cache.
* flushed my airport cache and renewed the DCHP lease.
* I had my machine off last night.
Turned it on this morning and loaded the same process. and it's happening everytime. That kind of replication and consistency suggests it's not just myclient flaking out correct?.
I mean it could be, but why ? It's like my client is flaking out because of the code loaded into it ? Maybe bad javascript or meta tags or something the browser need to process so it flakes out?
Anyway I just don't believe it's not a real error. There's more to it than clients flaking out.
T.
You'll get an "tcp error writing" when in your browser you navigate away from a page before the browser has finished downloading everything.
Usually Arc sends the entire response and closes the connection. When the browser doesn't wait, it closes the connection. Arc is then complaining that the connection has been closed on it.
If you're absolutely sure that everything has been loaded in the page before you click on anything, that would be something to look into further.
