Did it start to fail in version 1.4 or 1.4.5? Did it work in version 1.3.1?
Are you using the oauth authentication in REST Assured? What is the
actual URL that you try to access? (if it's a public URI it would be
good to know which one so I can try myself).
/Johan
https://graph.facebook.com///xxxxxx/accounts/test-users?access_token..If you remove the ending slash from the base uri it'll continue but you'll run into a "SSLPeerUnverifiedException". The reason why you don't see this in version 1.3.1 is probably because of an update of HTTP Client in REST Assured 1.4. You can read more about this here and you can refer to the documentation on how to solve it. If you know any better way (like how to tell HTTP Client to ignore unverified peers) let me know and I'll add support for it in REST Assured as well.