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
We're using Rails as an API backend to an Ember app using token auth. One issue I'm running into is we have a few API endpoints to download a file. Since we're no longer using cookies and since I can't set auth headers for a GET the download gets a big fat 401.
Is it possible to pass the token/email as query params for authenticating certain requests? If that suggestion makes your spidey sense go off, what's a good pattern for this case?
Thank you!
The text was updated successfully, but these errors were encountered:
You can set auth headers on a GET request
On Sat 16 May 2015 at 10:44 Jake Mauer [email protected] wrote:
Hey there!
We're using Rails as an API backend to an Ember app using token auth. One
issue I'm running into is we have a few API endpoints to download a file.
Since we're no longer using cookies and since I can't set auth headers for
a GET the download gets a big fat 401.
Is it possible to pass the token/email as query params for authenticating
certain requests? If that suggestion makes your spidey sense go off, what's
a good pattern for this case?
Thank you!
—
Reply to this email directly or view it on GitHub #246.
Hey there!
We're using Rails as an API backend to an Ember app using token auth. One issue I'm running into is we have a few API endpoints to download a file. Since we're no longer using cookies and since I can't set auth headers for a GET the download gets a big fat 401.
Is it possible to pass the token/email as query params for authenticating certain requests? If that suggestion makes your spidey sense go off, what's a good pattern for this case?
Thank you!
The text was updated successfully, but these errors were encountered: