Web Developer's Virtual Library: Encyclopedia of Web Design Tutorials, Articles and Discussions


WDVL Newsletter

Active Server Pages
JSP/Java Servlets
Microsoft SQL Server
Daily Backup
Dedicated Servers
Streaming Audio/Video
24-hour Support    

jobs.webdeveloper.com

Hiermenus


e-commerce
Partner With Us















Developer Channel
FlashKit.com
JavaScript.com
JavaScriptSource
Developer Jobs
ScriptSearch
StreamingMediaWorld
Web Developer's Journal
Web Developer's Virtual Library
WebDeveloper.com
Webreference
Web Hosts
XMLfiles.com

internet.com
IT
Developer
Internet News
Small Business
Personal Technology

Search internet.com
Advertise
Corporate Info
Newsletters
Tech Jobs
E-mail Offers


Problems With the GET Method

Problems With the GET Method

  • Though the GET method was very useful, a couple of serious problem remained.

  • First, the GET method only allowed a limited amount of data (1024 characters) to be sent as URL encoded data. 1

  • If there were too many name/value pairs, some of them would be clipped and data would get lost.

  • Further, since the information was sent as part of the URL, the user could see all of that data. On the one hand, that made URL's look really ugly and scary. On the other hand, it meant that the user got to see all of the inner workings of your CGI input.

  • This all changed with the development of HTTP/1.0.

Notes:

  • This wasn't implicit in the specs but in the limitations of OS restrictions, e.g. limited length of environment vars. Depending on the OS you might be able to send more or less than 1K.

The GET Method
Table of Contents
HTTP/1.0


Up to => Home / Authoring / Scripting / Tutorial




Jupiter Online Media: internet.comearthweb.comDevx.commediabistro.comGraphics.com

Search:

Jupitermedia Corporation has two divisions: Jupiterimages and Jupiter Online Media

Jupitermedia Corporate Info


Legal Notices, Licensing, & Permissions, Privacy Policy.

Web Hosting | Newsletters | Tech Jobs | Shopping | E-mail Offers