From the discussion in the ticket you've linked, it sounds like it shouldn't. I think we'd be happy to hear your argument though.

The main question here is: how to send an empty array to server?

Actually, this issue is related with $.param.

Duplicate of #6481.You're right, that is the question. How would you send an empty array using a form post without JavaScript? You wouldn't. The application/x-www-form-urlencoded MIME type doesn't support it. There is no governing standard or de-facto convention for how to send an array via a form.

The client and server can create any convention they'd like regarding what **string** might represent an empty array, but that's not something jQuery can help you with. We only handle the client end.

To send complex JavaScript-like data structures that don't resemble user form data entries, use JSON.

So you should remove $.param ability to send non-empty arrays.

Why can you send not empty array but you can't send empty array. This seems arbitrary.

It *is* arbitrary to some extent since there is no standard. We tried it both ways and this was the best compromise that broke the fewest things. Deal with it on your server, or convert the empty array to a string if you have no control over the server. You could also start lobbying to create a standard here, but I would guess that nobody would care enough to do anything about it since there are better solutions like JSON. Just don't blame jQuery, we can't read minds.

I do know you can't read minds, so I wrote a bug report instead of just blaming jQuery. :)

I do think people care about it, as I am not the first one complaining about empty array serialization.

jQuery already serializes arrays, just not the empty ones. The current array serialization format supports an empty array, jQuery just doesn't serialize it. Why?

Go back and read the old ticket. Summarize here.

I got it. The main problem is { a: [''] } would look like { a: [] }.

Thank for your attention.