Hello,

I've got a situation where a request to an OAuth protected resource is
generating a 400 response and populating the body of the response with
additional details.  But, when OAuthRequest sees the 400 response
status code it decides to go ahead and ignore the body of the response
from the service provider and replace it with it's own.  So, I have 2
questsions:

1) Why would it ever need to do that?  401 and 403 responses that are
OAuth specific are handled in the fetchData() method with the
checkForProtocolProblem(response) call.  If the response is not an
OAuth error, why would Shindig need to replace the actual response
body with one of it's own creation or do any extra work at all?

2) Is there a way to disable this behaviour?

Thanks,
Rich

Reply via email to