Oleg Kalnichevski wrote:
Jeroen van Vianen wrote:
I am trying to implement an interface to an OAuth server. OAuth
requires RFC 3986 [1] rather than RFC 1738 [2] encoding rules for
URIs, more specifically a space should be encoded as '%20' and not as
'+'. This breaks oauth_signature calculations.
Is there a way to use / force HttpClient into RFC's encoding rules on
GETs and POSTs?
No, there is not.
Consider migrating to HttpClient 4.0
But does HC 4.0 allow me to specify whether I want to use RFC 1738 or
3986 encoding rules? I could not find it. If I look in the code of HC
4.0 it uses URLEncoder.encode, which doesn't help either.
Thanks and best regards,
Jeroen
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
