This is similiar to curl --insecure (-k) where sometimes you don't want ssl verification.
Comment From: bclozel
Hi @selkhateeb - looks interesting! Could you create an issue on jira.spring.io for this? (project Spring Framework, component "Web:client")?
Also, I think adding this directly on the RestTemplate won't fit with all our supported clients (netty, okhttp, etc). This could be done only on the SimpleClientHttpRequestFactory
, as there are already some configurations facilities.
Comment From: pivotal-issuemaster
@selkhateeb Please sign the Contributor License Agreement!
Click here to manually synchronize the status of this Pull Request.
See the FAQ for frequently asked questions.
Comment From: ahrytsiuk
Hello @selkhateeb, @bclozel as I see this issue is not resolved yet, and this PR looks abandoned. I can propose my help.
@bclozel can you please guide me? Should I create a Jira ticket first?
Comment From: bclozel
Hi @ahrytsiuk
After checking this PR once more, it doesn't seem to be the right approach.
First, RestTemplate
is now in maintenance mode so we're not adding new features to it. Also, this is a feature that really belongs at the request factory level - and this really depends on the underlying client library. You should be able to achieve the same by configuring an SSL context on the client/factory that fits your need.
As a result, I'm closing this PR.
Comment From: ahrytsiuk
@bclozel I see your concern.
Maybe it's a good idea to add some autoconfiguration into Spring Boot project which can handle this functionality depends on underlying HTTP library?
Comment From: bclozel
I think you can already configure that on the client using the RestTemplateBuilder
.