Are Your CGIs Ready For HTTP 1.1 CONTENT_TYPE?
Friday July 30th, 1999
Eric Krock of Netscape has a second piece of news to pass along:
"The HTTP 1.0 CONTENT_TYPE line looked like this:
The HTTP 1.1 CONTENT_TYPE line looks like this:
Content-Type: application/x-www-form-urlencoded; charset=ISO-8859-1
In the interest of being standards-compliant and supporting multiple languages, Navigator 5 will support this feature of HTTP 1.1. Improperly designed CGI scripts that aren't forward-compatible with this change to the HTTP protocol will need to be fixed to support HTTP 1.1. Make sure your CGI scripts are ready for the HTTP 1.1 CONTENT_TYPE header. Read this new View Source article to find out how!"
Friday August 6th, 1999 5:49 AM
You are replying to this message
To all who are interested in: in the meantime I found a draft (via w3c) for Unicode in URLs (and therefore also in query strings):
So since w3c doesn't list any standards regarding this, Microsoft again makes its own standards...