- From: Neil Katin <katin@amorphous.com>
- Date: Fri, 9 Feb 1996 12:46:01 -0800
- To: NED@innosoft.com, fielding@avron.ICS.UCI.EDU
- Cc: http-wg%cuckoo.hpl.hp.com@hplb.hpl.hp.com
Ned said: > There are plenty of ways to approach this that do not require putting a hard > upper limit on URL size. For example, you could say that "all implementations > are required to support URLs at least 255 characters long and implementations > are encouraged to support URLs of as long a length as is feasible". You could also say that servers may not silently truncate or ignore URLs that are beyond their implementation limit; instead they must return a specific error (e.g. "URL too long"). This keeps implementations from taking the lazy way out and still being able to claim compliance with the spec.
Received on Friday, 9 February 1996 12:48:50 UTC