Ok found the answer. exchange() is the best way. Oddly the HttpEntity class doesn’t have a setBody() method (it has getBody()), but it is still possible to set the request body, via the constructor. // Create the request body as a MultiValueMap MultiValueMap<String, String> body = new LinkedMultiValueMap<String, String>(); body.add(“field”, “value”); // Note the body … Read more
I wish I still had a link to the source that lead me in this direction, but this is the code that ended up working for me. By looking over the JavaDoc for X509TrustManager it looks like the way the TrustManagers work is by returning nothing on successful validation, otherwise throwing an exception. Thus, with … Read more
You can mirror/proxy all requests with this: private String server = “localhost”; private int port = 8080; @RequestMapping(“/**”) @ResponseBody public String mirrorRest(@RequestBody String body, HttpMethod method, HttpServletRequest request) throws URISyntaxException { URI uri = new URI(“http”, null, server, port, request.getRequestURI(), request.getQueryString(), null); ResponseEntity<String> responseEntity = restTemplate.exchange(uri, method, new HttpEntity<String>(body), String.class); return responseEntity.getBody(); } This will … Read more
Errors you’ll see if a RestTemplate isn’t defined Consider defining a bean of type ‘org.springframework.web.client.RestTemplate’ in your configuration. or No qualifying bean of type [org.springframework.web.client.RestTemplate] found How to define a RestTemplate via annotations Depending on which technologies you’re using and what versions will influence how you define a RestTemplate in your @Configuration class. Spring >= … Read more
No, it is not a bug. It is a result of how the ParameterizedTypeReference hack works. If you look at its implementation, it uses Class#getGenericSuperclass() which states Returns the Type representing the direct superclass of the entity (class, interface, primitive type or void) represented by this Class. If the superclass is a parameterized type, the … Read more
The main problem here is content type [text/html;charset=iso-8859-1] received from the service, however the real content type should be application/json;charset=iso-8859-1 In order to overcome this you can introduce custom message converter. and register it for all kind of responses (i.e. ignore the response content type header). Just like this List<HttpMessageConverter<?>> messageConverters = new ArrayList<HttpMessageConverter<?>>(); //Add … Read more
No, RestTemplate will continue to exist (at least for now). You don’t have to replace it with WebClient. One of the main differences is RestTemplate is synchronous and blocking i.e. when you do a rest call you need to wait till the response comes back to proceed further. But WebClient is complete opposite of this. … Read more
ParameterizedTypeReference has been introduced in 3.2 M2 to workaround this issue. Wrapper<Model> response = restClient.exchange(loginUrl, HttpMethod.GET, null, new ParameterizedTypeReference<Wrapper<Model>>() {}).getBody(); However, the postForObject/getForObject variant was not introduced.
You’re not missing anything. RestTemplate#exchange(..) is the appropriate method to use to set request headers. Here’s an example (with POST, but just change that to GET and use the entity you want). Here’s another example. Note that with a GET, your request entity doesn’t have to contain anything (unless your API expects it, but that … Read more
Taken from the example on this site, I think this would be the most natural way of doing it, by filling in the header value and passing the header to the template. This is to fill in the header Authorization: String plainCreds = “willie:p@ssword”; byte[] plainCredsBytes = plainCreds.getBytes(); byte[] base64CredsBytes = Base64.encodeBase64(plainCredsBytes); String base64Creds = … Read more