On 19/07/13 21:52, mayankeagle wrote:
Its 2.6.2 right now. I think I figured the problem. We had written a custom
OOB response provider (with your help) in
http://cxf.547215.n5.nabble.com/OAuth-1-0-in-CXF-2-6-2-td5713150i20.html and
the response returned from there was being URL encoded. I'll remove that
part from the code and check again, and let you know!
I've checked with my demo, works as expected, see a log fragment:
Response from the decision handler:
ID: 12
Response-Code: 303
Content-Type:
Headers:
{Location=[http://localhost:8080/services/reservations/reserve/complete?oauth_token=79ff44f9-fe2b-4e1d-8a09-820eff861df8&oauth_verifier=02d6fff7-7031-49be-8f60-a89db36ff5d0],
Date=[Fri, 19 Jul 2013 20:57:39 GMT], Content-Length=[0]}
This is the browser following a redirect:
--------------------------------------
19-Jul-2013 21:57:40 org.apache.cxf.interceptor.LoggingInInterceptor
INFO: Inbound Message
----------------------------
ID: 13
Address:
http://localhost:8080/services/reservations/reserve/complete?oauth_token=79ff44f9-fe2b-4e1d-8a09-820eff861df8&oauth_verifier=02d6fff7-7031-49be-8f60-a89db36ff5d0
Http-Method: GET
So indeed - must be something to do with your OOB provider implementation
Cheers, Sergey
--
View this message in context:
http://cxf.547215.n5.nabble.com/CXF-Date-marshalling-issue-tp5731091p5731171.html
Sent from the cxf-user mailing list archive at Nabble.com.
--
Sergey Beryozkin
Talend Community Coders
http://coders.talend.com/
Blog: http://sberyozkin.blogspot.com
