MAX_REQUEST_PATH_LENGTH = 1024; Why?

[mdimas]

Why is there a limit placed on the path length? Especially one that is considerably smaller than the one imposed by any browser. When working with paths that contain non-ascii characters that need to be encoded the length can frequently by longer than 1024 characters.

Is there a way to override this setting?

[evanphx]

It's something that the parser inherited from mongrel, but we can certainly change it. What do you think a good value is?

[mdimas]

Thanks for looking at this so quickly.

According to the RFC "The HTTP protocol does not place any a priori limit on the length of a URI." It appears that IE enforces the shortest maximum at 2083 bytes, with other browsers supporting much higher limits. It seems like at least allowing 2083 would be nice, or maybe not enforcing anything at all since it isn't defined in the standard.

[mdimas]

@evanphx any estimate on when a release with the higher maximum will be available?

[priyankc]

Made a fix to increase URI path length to 2048. Included tests to validate.

[ghost]

@mdimas : #408 was merged to increase the max length to 2048 (as per HTTP RFC), so you can likely close this ticket now

[evanphx]

This has been changed to 2048.

[ryandotsmith]

Is it worth the effort of making this configurable via puma config? I am in a situation where I would like to have this value be much larger than 2048.

[ryandotsmith]

rfc2616 3.2.1

The HTTP protocol does not place any a priori limit on the length of a URI. Servers MUST be able to handle the URI of any resource they serve, and SHOULD be able to handle URIs of unbounded length if they provide GET-based forms that could generate such URIs. A server SHOULD return 414 (Request-URI Too Long) status if a URI is longer than the server can handle (see section 10.4.15).

http://www.w3.org/Protocols/rfc2616/rfc2616-sec3.html