Maurits wrote:As long as it's mis-spelled the same way every time... (see RFC 2616 14.36)
How the heck did that mistake make it through to HTTP1.1?
Backwards compatibility. You don't want o break clients that still use HTTP1.0
Or the non-standards way (that works in older browsers and also has no memory leak):