diff options
| author | James Tucker <jftucker@gmail.com> | 2013-04-21 13:37:52 -0700 |
|---|---|---|
| committer | James Tucker <jftucker@gmail.com> | 2013-04-21 13:38:21 -0700 |
| commit | 1dda287141a30ceb6e55c8ad877a6f907558e98d (patch) | |
| tree | 712970a9d00b089e5146c7d820cb7f09d9f0af5b | |
| parent | 28e10895f2925b354627de1443d76372315f9795 (diff) | |
| download | rack-1dda287141a30ceb6e55c8ad877a6f907558e98d.tar.gz | |
Add note about parameter parsing not changing
| -rw-r--r-- | KNOWN-ISSUES | 14 |
1 files changed, 14 insertions, 0 deletions
diff --git a/KNOWN-ISSUES b/KNOWN-ISSUES index e0373b2f..129b582f 100644 --- a/KNOWN-ISSUES +++ b/KNOWN-ISSUES @@ -28,3 +28,17 @@ Since lighttpd 1.4.23, you also can use the "fix-root-scriptname" flag in fastcgi.server. + += Known conflicts regarding parameter parsing + + * Many users have differing opinions about parameter parsing. The current + parameter parsers in Rack are based on a combination of the HTTP and CGI + specs, and are intended to round-trip encoding and decoding. There are some + choices that may be viewed as deficiencies, specifically: + - Rack does not create implicit arrays for multiple instances of a parameter + - Rack returns nil when a value is not given + - Rack does not support multi-type keys in parameters + These issues or choices, will not be fixed before 2.0, if at all. They are + very major breaking changes. Users are free to write alternative parameter + parsrs, and their own Request and Response wrappers. Moreover, users are + encouraged to do so. |