Re: [whatwg/url] Allow encoding of null values in `application/x-www-form-urlencoded`. (Issue #732)

Thanks @ioquatix for bringing this up from Grape and @domenic and @annevk for your comments! 

Y'all make a ton of sense, even though I think you are too focused on browsers, which are like people, a bit unpredictable at times. In contrast, I think most API developers that were not forced into using `application/x-www-form-urlencoded` by a form filled in a browser abandoned it in favor of `application/json` for lack of clarity for things like nulls in URLs and different server-side interpretations. With the change introduced by Rack strictly interpreting the standard they should not be relying on query string parameters either. We can stay true to the spec. 

My conclusion is that it was nice when the implementation allowed nulls in a non-ambiguous way In Grape! What @ioquatix was suggesting is to restore that, but I agree that we're extending the spec by doing so. We plan to cleanly deprecate that behavior, tell our users that it's now undefined, and call it a day.

-- 
Reply to this email directly or view it on GitHub:
https://github.com/whatwg/url/issues/732#issuecomment-1372182859
You are receiving this because you are subscribed to this thread.

Message ID: <whatwg/url/issues/732/1372182859@github.com>