Manually added Authorization header does funny things

[bbredewold]

I have checked the following:

• I use the newest version of bruno.
• I've searched existing issues and found nothing related to my issue.

Describe the bug

So, when adding an 'Authorization' header, I need to fill it with a custom value. So not a 'Bearer'-token' but an 'AfasToken'-token. As you can see in the screenshot, Bruno assumes a Bearer token anyway. This way I cannot use Bruno to make requests to AFAS.

I assume the Authorization header is overwritten from the Collection. But I expect that when I set the same header on the request itself, it should overwrite the one from the collection.

Screenshots/Live demo link

[GarlicPunk]

You can try using a pre-request script to req.setHeader instead of using the form.

req.setHeader("transaction-id", nanoid());

[bbredewold]

You can try using a pre-request script to req.setHeader instead of using the form.

req.setHeader("transaction-id", nanoid());

That seems to be a bit cumbersome for such a basic feature.
Imho request-set headers should always overwrite the Collection-set headers.

[pietrygamat]

@bbredewold when that happens - what is the authorization mode used for your request? Is it inherit, None, or Bearer token? It looks to me that the problem is your request Auth overwriting your manually set header, but that should not happen when using auth mode = 'none' .

[lohxt1]

Imho request-set headers should always overwrite the Collection-set headers.

this is the current default behaviour

request_headers_over_collection_headers.mov

you can choose auth type as none, and set the AfasToken directly either through the header or via script

afastoken.mov