问题
What is the right way to make a very long get request?
For example, to get a table or report of a lot of stuff from a big database, the client has a filter and can choose from a long list of over 300 choices (multi-select). If he chooses to select all, or almost all of them, the created URL params sent to the server will be so many that it makes the URL too big.
I have thought of some ways to reduce redundancy that will make the URL smaller. But in case this doesn't work, and for future knowledge, what is the right way to make long get requests? Do they have to be "split up", and if so, does the server have to first store the 1st half and then read it during the 2nd get request?
来源：https://stackoverflow.com/questions/20809244/very-long-http-get-request