Headers per Collection

[moelena]

Hello,

thank you for providing this great tool.
Since I just switched from Postman and have to do repetitive steps to set up all the requests I need, I have a few suggestions. One of them:

In my API I have to do a login call first (and save the received token in an environment variable) and then call any other request. In every other request I have to set up the same headers: Authorization with token from the environment and custom headers.
It would be very nice, if I could define the headers in the collection. Or if I could set the headers with the request script (when it works collection-wide: #63).

[jonrosner]

Thank you for the feedback. Highly appreciated. Would it be possible for you to create a separate issue for all of the feature requests so we could track them individually?

[moelena]

Sure, no problem. I also edited the text above.

[jonrosner]

I'll look into how other tools do this. Right now having a collection-level request script method called setHeader makes the most sense to me.

[moelena]

That would be totally fine for me. In Postman I did that also per script:
pm.request.headers.add({key: 'User-Agent', value: 'myAgent' });

[jonrosner]

Collection wide headers are added in the newest version.