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

#8 Re: Backward Compatibility

by Anon

Sunday August 1st, 1999 6:21 AM

You are replying to this message

Actually, no. You see, badly written CGIs have been a major problem (can you say ?something&param1&param2) for quite some time. If we're going to go standard-compliant, we will have to take the chance of "breaking" badly designed code in some areas. And Mozilla won't exactly "crash on all the CGI scripts it used to handle just fine". It will crash some badly written CGIs which can't handle the W3C standard, I think.