Jeremy Evans

This is expected behavior if you are using an incorrect line terminator (`\n` is incorrect, you must use `\r\n`, see RFC 1341 section 7.2.1). In rack 3, you get `Rack::Multipart::EmptyContentError`...

I don't think it is worth adding an alias for `params`.

I don't think it is appropriate to do this by default in Rack (doing so would unfairly favor a single vendor, and results in a slippery slope). However, I would...

This was fixed by #2089

I would prefer to leave this unspecified. In this case, I don't think the advantages of specifying it (consistency between implementations) outweigh the costs (requiring the server to convert an...

I would prefer to leave the SSL behavior unspecified, and close this.

This is a bug in the application that needs to be fixed, not a bug in Rack. That it worked in older versions of Rack is accidental.

We could change `article_version[body[answer1]]=` to parse as `{"article_version"=>{"body[answer1]"=>""}}` instead, by keeping count of the number of `[` and `]`. That would make slightly more sense than the current parsing. But...

To reiterate for clarity, we aren't going to support parsing `article_version[body[answer1]]=` as `{"article_version"=>{"body"=>{answer1"=>""}}}`. Trying to support that brings more complexity and results in two separate ways to support the same...

If you use the correct parameter name, `article_version[body][answer1]=`, then it will work in all versions of Rack. Please understand that the fact that `article_version[body[answer1]]=` worked in older versions of Rack...