Allow overriding the Host header
Feature Request
Requests currently ignore a user-provided Host header, which blocks workflows that depend on setting it manually.
Example from a user: simulating a valid HTTP call to an AWS ELB requires sending a Host header that doesn’t match the request URL — without an override, the call can’t be made to work in Yaak.
Expected behavior: if a Host header is explicitly set on the request, send it as-is instead of deriving it from the URL.
Possibly related: Import from cURL with Host Header cause 400 bad request may share the same underlying header handling.