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
When I do a GET on a binary resource the data I get back is corrupted. Please see below for the oada-cache call I tried and then an axios request which returns the correct data.
On Sat, Jan 25, 2020, 7:25 PM Alex Layton ***@***.***> wrote:
When I do a GET on a binary resource the data I get back is corrupted.
Please see below for the oada-cache call I tried and then an axios request
which returns the correct data.
const { data, headers } = await conn.get({ path })
const { data, headers } = await axios.get(path, {
baseURL: domain,
headers: { Authorization: `Bearer ${token}` },
responseType: 'arraybuffer'
})
Perhaps all that is needed to address this is a way to ask oada-cachefor
an arraybuffer response.
—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub
<#10?email_source=notifications&email_token=AAOHLBM644WUFBDYC2ZGLXDQ7TJ77A5CNFSM4KLT5RAKYY3PNVWWK3TUL52HS4DFUVEXG43VMWVGG33NNVSW45C7NFSM4IIXBQKA>,
or unsubscribe
<https://github.com/notifications/unsubscribe-auth/AAOHLBNOFVJXIV5H6WYUC4DQ7TJ77ANCNFSM4KLT5RAA>
.
When I do a GET on a binary resource the
data
I get back is corrupted. Please see below for the oada-cache call I tried and then an axios request which returns the correct data.Perhaps all that is needed to address this is a way to ask oada-cachefor an
arraybuffer
response.The text was updated successfully, but these errors were encountered: