2 ms·
While there's nothing stopping you from doing so I would be wary about it. Even though the service will be internal you might still need to use third-party soft
by dmlittle 7y ago
While there's nothing stopping you from doing so I would be wary about it. Even though the service will be internal you might still need to use third-party software/tools in the future that will be incompatible because of this.
For example, will you need to use a 3rd party request library? Will you need to set up some sort of proxy (NGINX, HAProxy, etc.)? Will you need to use a cloud load balancer (I'm not sure if they would send a request payload for GET requests)?
For open-source solutions you might be able to fork them to add this behavior but why do so to begin with? Is there a specific reason why you don't want to use query parameters?
- larryfreeman 7y agoAt this point, we have tested all 3rd party request libraries that we will be using. It is possible that DevOps could change start using a new one in the future that would not support a GET request with body. I agree that it is well worth keeping this in mind and checking on the state of third party support. Would you happen to know which popular 3rd party tools do not currently support a GET with request body?