In our legacy fork, we had handling for what seems like a case where the fallback is called and tries to be parsed as JSON, even though it's XML response data. What appeared to be happening was options[:format] was not specified, but it needed to be or else JSON would be defaulted to.
So, let's try reproduce that bug and put a proper fix in place, if indeed it's still happening (or was some other issue).
In our legacy fork, we had handling for what seems like a case where the fallback is called and tries to be parsed as JSON, even though it's XML response data. What appeared to be happening was
options[:format]was not specified, but it needed to be or else JSON would be defaulted to.So, let's try reproduce that bug and put a proper fix in place, if indeed it's still happening (or was some other issue).