When the request parameter in HTTP is an array, when do I need to add square brackets [] to the parameter name?

Android (Retrofit) Request code

@FormUrlEncoded@POST("util/pinyin")Call> pinyin(@Field("lrcs[]") String[] lrcs);

For example, you can get the correct request result, and the ' @Field ("LRCs") ' server can only receive the last element of the array I sent out.
I caught my own bag to see that the confirmation was all contained in the post body sent out.

Is this the limit of the service-side parsing framework? Or is the HTTP protocol required? Or is it a formurlencoded limit?

Using square brackets (square brackets) + http/post do not find anything associated with the result.

Reply content:

Android (Retrofit) Request code

@FormUrlEncoded@POST("util/pinyin")Call> pinyin(@Field("lrcs[]") String[] lrcs);

For example, you can get the correct request result, and the ' @Field ("LRCs") ' server can only receive the last element of the array I sent out.
I caught my own bag to see that the confirmation was all contained in the post body sent out.

Is this the limit of the service-side parsing framework? Or is the HTTP protocol required? Or is it a formurlencoded limit?

Using square brackets (square brackets) + http/post do not find anything associated with the result.

Requirements for the HTTP protocol

When parsing parameters, the same key overwrites the previous one,
If the band [] is treated as a one-dimensional array, it will not overwrite the

