You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Summary or problem description
Currently oracle only allow mime type application/json and if the server returns a mime type of application/json; charset=utf-8. This will invalidate the oracle request and throw an error code of 31.
Do you have any solution you want to propose?
Fix the logic to allow any mime type of application/json
Where in the software does this update applies to?
Oracle
The text was updated successfully, but these errors were encountered:
This limitation existed since the oracle implementation.
But I never really understood it, it looks artificial and not helpful in any way. So I'm for allowing more, in general.
We at the same time have JSON filters in the API now and this complicates the matter, we can't just enable any MIME types at the oracle module level, filter + non-JSON reply can't work.
So maybe we need an additional request API at the oracle contract level for non-JSON things.
I think that currently it is not necessary, with json should be sufficient for current services, I also think that it's more interesting an aggregator of different sources, usually oracle is used for prices, and all the apis produce json
Summary or problem description
Currently
oracle
only allow mime typeapplication/json
and if the server returns a mime type ofapplication/json; charset=utf-8
. This will invalidate the oracle request and throw an error code of31
.Do you have any solution you want to propose?
Fix the logic to allow any mime type of
application/json
Where in the software does this update applies to?
The text was updated successfully, but these errors were encountered: