Authorization header gets scrambled when coming from environment variable?

[erzz]

config:
  target: "https://mysite.com"
  phases:
    - duration: 60
      arrivalRate: 5
      name: Warm up
    - duration: 120
      arrivalRate: 1
      rampTo: 40
      name: Ramp up load
    - duration: 120
      arrivalRate: 40
      name: Sustained load
scenarios:
  - name: "filters"
    flow:
      - log: "{{ $processEnvironment.ID_TOKEN }}"
      - get:
          url: "/search/ru/ph/filters"
          headers:
            Authorization: "{{ $processEnvironment.ID_TOKEN }}"

In the above case every request results in errors.ERR_INVALID_CHAR

The value of ID_TOKEN is Bearer long-jwt and the log I added above presents it correctly. In fact I copy from that log and use it in the browser and it works there.

If I replace the environment variable in the config with Authorization: "Bearer long-jwt" it works fine. The issue is only when trying to use it as a variable

[hassy]

hi @erzz 👋 that sounds very odd! could you double-check the value of ID_TOKEN does not contain any newlines?

[erzz]

It did not.

An update is that if I remove the "Bearer " out of the environment variable and into the config it works fine (so solved from that perspective) but still strange.

So to be clear:

Gives errors.ERR_INVALID_CHAR

export ID_TOKEN="Bearer <long-jwt"
...
headers:
  Authorization: "{{ $processEnvironment.ID_TOKEN }}"

Works

export ID_TOKEN="<long-jwt"
...
headers:
  Authorization: "Bearer {{ $processEnvironment.ID_TOKEN }}"

So I am happy enough in that I have a working config - but perhaps someone else can replicate