MozillaZine

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


#10 badly written scripts??

by kidzi

Tuesday August 3rd, 1999 4:14 PM

You are replying to this message

when you say script?param&param&param.. is that the wrong whereas script?name=param&name=param&... etc would be considered OK?? I use the get often for scripts because it is bookmarkable.. i've never used this content stuff you'r talking about, and i've been working wiht scripts for almost 3 years now :P .. i have used content-type: text/html... and a few other mime's, but that's the general structure!! HELP!!!

<kevin@idzi.com>