Re: [rest-discuss] REST and URL length limitations
- On 4/30/07, hovhannes_tumanyan <hovhannes_tumanyan@...> wrote:
>More restrictive than that is the IIS path length limitation of (up
> Please, excuse my ignorance, if this was discussed earlier but did
> anyone consider the impact of URL size limitation on RESTful
> application implementation in real world?
> To the best of my knowledge, RFC do not limit the size of URL or GET
> query string. However, quick research on the net suggests that IE, for
> instance, can't accommodate more than 2083 characters. I'm inclined to
> believe that 2083 characters (not bytes) essentially is the limit of
> state information that can be included in RESTful request.
> In reality, the real limit is even lower due to URLencoding
> Any thoughts or comments are highly appreciated and welcomed!
to) 260 characters.
I don't know if other web servers suffer the same limitation.
Essentially, IIS assumes that the path represents a physical file and
applies the windows MAX_PATH length (this won't affect anything after
? or # in the URI). If you nest the virtual directory deep inside the
file system, this will reduce the supported path length even further.
- Isn't it actually unfortunate that IE (or some browser) has a limitation?
Does the XMLHttpRequest object have the same limitation?On 4/30/07, Steve Bjorg <steveb@...> wrote:Yes, it's really unfortunate that GET can't take a body. :( You could do a POST with Content-Type set to application/x-www-form-urlencoded and then use the X-HTTP-Method-Override header to override the http method to be GET. Probably not a good idea though.