Hi Dan, Thanks. I was earlier URL decoding the response, hence the + was creating an issue.
But I also noticed that the CXF OAuth API is returning me the verifier with encoding but the remaining parameters without encoding. e.g., the call to /initiate returns oauth_token=....&oauth_token_secret=.... However, when it responds to /authorize/decision and sends the verifier, it comes as oauth_verifier%3D.... (the = has been encoded as %3D) Hence, I am unable to parse the response in a consistent manner, as CXF is sending some responses as URL encoded and some as not! -- View this message in context: http://cxf.547215.n5.nabble.com/CXF-Date-marshalling-issue-tp5731091p5731168.html Sent from the cxf-user mailing list archive at Nabble.com.
