--- Maciej Stachowiak [EMAIL PROTECTED] wrote:
On Mar 7, 2008, at 3:02 PM, Morgan L wrote:
Ah, that make sense to me. I think the current
text
has caused major browser engines to mistakenly
stop
supporting connection: close. It is easy to
blindly
implement whatever
--- Bjoern Hoehrmann [EMAIL PROTECTED] wrote:
* Morgan L wrote:
In section 2 of
http://www.w3.org/TR/XMLHttpRequest/,
it says that setRequestHeader should reject the
connection header.
The purpose of these restrictions is to remind
implementers that the
user agent has to control
Hi, I'm writing about what appears to be an error in
the XHR TR.
In section 2 of http://www.w3.org/TR/XMLHttpRequest/,
it says that setRequestHeader should reject the
connection header.
However, there are web apps in existence (e.g., Gmail)
that set the connection: close header to inform the
