GraphQL mode ignores manual Content-Type header override
Bug
When using a GraphQL request in Yaak, the Content-Type header appears to be set internally and cannot be overridden by manually adding a Content-Type header in the Headers tab.
Use case: I’m working against a GraphQL server that has introspection disabled. The server does not expose its schema and treats the payload as plain JSON. When I try to set a custom Content-Type (e.g. application/json with specific parameters, or any non-default value), the header I define is either ignored or the request is sent with the value Yaak decides internally.
macOS2026.3.1
https://yaak.app/changelog/2026.4.0
https://github.com/mountain-loop/yaak/releases/tag/v2026.4.0-beta.1
Thanks for the report! Fixed in dev
Thanks for your response. Apologies for not being clearer in my initial message—I realize I didn’t properly explain my use case.
What I actually need is to be able to set the Content-Type header to application/graphql. My GraphQL server has introspection disabled, so Yaak falls back to forcing application/json internally. However, my server expects application/graphql and won’t accept the request otherwise.
When I try to manually add a Content-Type header in the Headers tab, it gets ignored or overridden by Yaak’s internal value. This makes it impossible to work with servers that require application/graphql when introspection is disabled.
It would be great if users could override this behavior or if Yaak provided an option to choose which Content-Type to send for GraphQL requests, regardless of whether introspection succeeds or not.
Thanks again for your help.