Was going to delete this item but maybe someone will find this useful. I assumed JS was active since the query string contained the variable "post_form_id_source=AsyncRequest" which to me seemed like an obvious nod the now ubiquitous xmlHTTPRequest being used. While it doesn't prove conclusively that there wasn't JS running, it does make it plausible that it was purely an HTTP connection kept alive by X-Cnoection header. Im still fuzzy as to how this works or how its done but ill post a quick excerpt of what i found after some searching:

"Missed Cneonctions

This header:

Cneonction: close and its variant:

nnCoection: close were two of the headers which first spurred my interest in HTTP headers.

imdb.com, amazon.com, gamespy.com, and google.com have all at various times used these or similar misspellings of connection, and I’m not by any means the first to have noticed. My first thought was that this was just a typo. After more consideration, however, I now believe this is something done by a hackish hardware load balancer trying to “remove” the connection close header when proxying for an internal server. That way, the connection can be held open and images can be transmitted through the same TCP connection, while the backend web server doesn’t need to be modified at all. It just closes the connection and moves on to the next request. Ex-coworker and Mudd alumus jra has a similar analysis."

source: http://www.nextthing.org/archives/2005/08/07/fun-with-http-h...