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
Using version 1.0.0, when set up my project with an authorization header, (in my case, a jwt token) then configure an environment pointed at my local development server, then click the "Refresh" link, the request is sent WITHOUT the header configured at the project config page.
(Incidentally, it would be more useful to me to be able to configure headers per-environment than per-project, but that's a different ticket...)
What I expected was to see the authorization header listed in the request headers for the request when observing it in the web developer console network tab.
The text was updated successfully, but these errors were encountered:
Using version 1.0.0, when set up my project with an authorization header, (in my case, a jwt token) then configure an environment pointed at my local development server, then click the "Refresh" link, the request is sent WITHOUT the header configured at the project config page.
(Incidentally, it would be more useful to me to be able to configure headers per-environment than per-project, but that's a different ticket...)
What I expected was to see the authorization header listed in the request headers for the request when observing it in the web developer console network tab.
The text was updated successfully, but these errors were encountered: