A modern programming language that makes developers happier.

kotlinlang

I have stumbled into this due to caching issues. I am implementing an endpoint that should be cacheable, and semantically should be a GET request, but the request has a lot of parameters that aren't realistic to include as query parameters. Since I control the server I thought I would just send it as a body, but discovered I can't send a body with a GET request using Retrofit. I can't use POST either because then it isn't cacheable. Both problems (and the explanations in this thread) make perfect sense, but what is the proper solution here?

What is the proper solution to having a cacheable API endpoint that has a request that won't fit in query parameters?