We have introduced sending searches using POST, which keeps the parameters safely in the encrypted body and allows for parameter values that may cause problems using a GET (i.e. because of length).

However, we also say that for paging servers will create prev/next links and a self link that contain the parameters that the server understands.

This causes two problems:

• Paging is always done as a GET, so you are switching from POST to GET when accessing other pages – this is probably an undesired effect as there might be good reasons (some of which I mentioned) to use POST in the first place, and you'd want the paging to occur on a POST too.

• For some of the same reasons, you may not even be able to express the parameters on the POST as a parameter on a GET (length being one of the reasons).

I wonder if there is any way to improve this....