Api: Question: CORS using Origin Header for Browser Based Apps

Created on 2 Sep 2017  路  4Comments  路  Source: Bungie-net/api

Heyo, quick question about how the Browser Based Apps are supposed to work.

I assumed that If I filled out this section on https://www.bungie.net/en/Application/:

screen shot 2017-09-01 at 9 04 25 pm

waited some time, then tried to hit an endpoint via browser only (no proxy), I'd be able to get data back.

However, I am still getting blocked:

screen shot 2017-09-01 at 9 03 34 pm

Am I doing something wrong? is this functionality just not ready yet?

Thanks!

Most helpful comment

Looks like you're missing www. Need that www I believe. Also watch out for the trailing slash in the future.

Check this for detail OAuth info
https://lowlidev.com.au/destiny/authentication-2

All 4 comments

just for reference, the browser is sending the same Origin header as I've entered for my app:

screen shot 2017-09-01 at 9 09 11 pm

Double check your x-api-key header and API key value is correct. When I got that error I had the x-api-key header wrong(copy/paste issue in API key), so the Bungie servers couldn't lookup my app to find the Origin Header setting to match what was being sent.

Here is a help article too

Looks like you're missing www. Need that www I believe. Also watch out for the trailing slash in the future.

Check this for detail OAuth info
https://lowlidev.com.au/destiny/authentication-2

oh man @lax20attack yeah it was the missing www. Once I put that in there everything worked as expected. ugh. late nights are rough.

Was this page helpful?
0 / 5 - 0 ratings

Related issues

rentalhost picture rentalhost  路  4Comments

cortical-iv picture cortical-iv  路  4Comments

mikewojtkiewicz picture mikewojtkiewicz  路  3Comments

andyschott picture andyschott  路  3Comments

soren42 picture soren42  路  3Comments