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
As we have recently switched to Insomnia as our go-to REST client tool (especially for GraphQL) in our Dev environment, we’ve seen a lot of great features in the app. This near-perfection of the tool has also outlined a feature that is, in our opinion, missing: Global Headers. If users can set the headers the way variables can be set, the app will be more dynamic. We have a couple dozen queries we test, and need to apply some header-tokens to all of them to make sure they pass verification. In the current situation, our queries have headers with variable values, with the values entered on sub-domain level. However, if for example headers are changed or added in the future, we’d have to make the same change to every query.
Another example; when a user is logged in, all the following calls will need an Authorization header consisting of a JWT token. With which the back-end determines if and what user is logged in. Without global headers, we need to update our headers in every query we test with the freshly created JWT token. If we could add this as a Global Header, calls would work immediately with the correct headers set globally.
We believe these examples highlight several use cases that would significantly benefit from the addition of the requested feature.
The text was updated successfully, but these errors were encountered:
Feature Request: Global Headers
As we have recently switched to Insomnia as our go-to REST client tool (especially for GraphQL) in our Dev environment, we’ve seen a lot of great features in the app. This near-perfection of the tool has also outlined a feature that is, in our opinion, missing: Global Headers. If users can set the headers the way variables can be set, the app will be more dynamic. We have a couple dozen queries we test, and need to apply some header-tokens to all of them to make sure they pass verification. In the current situation, our queries have headers with variable values, with the values entered on sub-domain level. However, if for example headers are changed or added in the future, we’d have to make the same change to every query.
Another example; when a user is logged in, all the following calls will need an Authorization header consisting of a JWT token. With which the back-end determines if and what user is logged in. Without global headers, we need to update our headers in every query we test with the freshly created JWT token. If we could add this as a Global Header, calls would work immediately with the correct headers set globally.
We believe these examples highlight several use cases that would significantly benefit from the addition of the requested feature.
The text was updated successfully, but these errors were encountered: