- From: Yves Lafon <ylafon@w3.org>
- Date: Wed, 24 Aug 2005 18:54:30 +0200 (MEST)
- To: Paul Cooper <paulcooper@digital-magic.co.uk>
- cc: www-validator-css@w3.org
On Wed, 24 Aug 2005, Paul Cooper wrote: > > Ah, yes. Thanks guys. That'll be the problem. > Strange they chose GET and not POST. Forgot the limit for GET was so low. There is no limitation per RFC2616, just a de-facto limitation because of the bugs in some browsers (that may be replaced by newer versions without this bug in the future). So I am not keen on misusing the HTTP verbs only to do a bug workaround. > > Anyway. Thank you again > > Paul Cooper > >> -----Original Message----- >> From: www-validator-css-request@w3.org >> [mailto:www-validator-css-request@w3.org]On Behalf Of Jukka K. Korpela >> Sent: 24 August 2005 05:57 >> To: www-validator-css@w3.org >> Cc: Paul Cooper >> Subject: Re: direct input limit? >> >> >> >> On Wed, 24 Aug 2005, Bjoern Hoehrmann wrote: >> >>> Sounds like you are using Internet Explorer or similar which indeed >>> does not submit forms using GET if there is more than a certain amount >>> of data (~2K IIRC). >> >> According to Microsoft, the limit is 2,083 characters for a URL and >> 2,048 characters ("2K") for a path inside a URL: >> http://support.microsoft.com/default.aspx?scid=kb;EN-US;q208427 >> >> This implies that using the GET method, there is an upper limit for the >> amount data. The exact limit depends on the form, since the URL in the >> action attribute and names of fields as well as punctuation required by >> the syntax affect the length of the URL that the browser constructs upon >> submission. >> >> -- >> Jukka "Yucca" Korpela, http://www.cs.tut.fi/~jkorpela/ >> >> >> >> > > > -- Yves Lafon - W3C "Baroula que barouleras, au tiéu toujou t'entourneras."
Received on Wednesday, 24 August 2005 16:56:17 UTC