Not simple at all.
Bodies in GET requests have no defined meaning, according to RFC 7231. Any server or proxy you are dealing with is perfectly within its rights to drop your body on the floor.
There are conventions for REST endpoints, among them that GET requests cannot modify externally visible state and may be repeated an unspecified number of times without adverse effect.
They really are for queries - getting things. If you need to specify query parameters, use
HttpParams - they will be appended to the query string of the URL.
If you don’t want the stuff you are trying to put in the body in the URL, that is a very strong indicator that the endpoint is misclassified in the first place, and should be a POST instead (or a PUT if you’re OK with it being done multiple times).
If you would like to give more detail as to what this endpoint does, perhaps you will get some more feedback on whether you should move the body stuff into the URL and stick with GET or leave the body stuff in the body and switch to another method.
Those are the only standards-compliant options, which is why Angular’s
HttpClient does not take bodies in its