Closed nonchip closed 3 years ago
yeah, that's a common issue, sadly we don't have a way around it. it's hit and miss when, if ever, it works.
we have this integrated into our api (https://api.warframestat.us/profile/{username}
), and have precisely the same problem
@TobiTenno ok i'm slightly confused now, if this is a problem, and even your api can't get to the data half the time, and it's still documented "wrong", why close the ticket? shouldn't it be better kept open in case anyone can provide further insight (e.g. i've heard murmurs on the reddits about that "auth header" being some rolling key generated by twitch, which would kinda suck to try and interface against)? given it's still an ongoing issue. or is there some other place where "investigation" into this happens you could point me to?
Because I don't believe it will ever be fixed and I always close said tickets.
Also, as demonstrated from the example in the readme, the fetch occurs however the user decides, so it's not something this library handles. So even if the fetch doesn't work, parsing data still works fine when real data is provided to the library
yeah, that's a common issue, sadly we don't have a way around it. it's hit and miss when, if ever, it works.
to further reinforce this, right now:
but also
tried it with your example usage, but i get:
trying to access my own arsenal by browsing to the address manually also returns:
so apparently there's some header missing, presumably with an api key of some sorts? how would I a) get that and b) provide it to the
fetch
call?