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:

Content-Type: application/x-www-form-urlencoded

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!"

#11 Are Your CGIs Ready For HTTP 1.1 CONTENT_TYPE?

by Anon

Wednesday August 4th, 1999 10:03 PM

You are replying to this message

Just wanted to emphasize: Mozilla is going to send along the chosen enconding and *only* CGI scripts which check the HTTP Content-Type they *got* will get broken. In my experience, that are not so many.