context.call assumes a content-type erroneously.

[undrscrdt]

When fetching a JSONL file from google storage using context.call (context.call(url, {method: "GET"})), it returns a 403 error because the signature does not match the request. The reason for this is that the header "Content-Type" is not expected. Setting the header to "undefined" or "null" does not work because the header isn't removed, it simply is assigned those values.

https://github.com/upstash/workflow-js/blob/main/src/qstash/headers.ts#L209

const contentType =
      (callHeaders.get("content-type")
        ? callHeaders.get("content-type")
        : this.userHeaders?.get("Content-Type")
          ? this.userHeaders.get("Content-Type")
          : undefined) ?? DEFAULT_CONTENT_TYPE;
    this.headers.rawHeaders["content-type"] = contentType;

Headers should not be set when undefined.

[CahidArda]

Hi @thecrowkeep,

When writing this, we thought it would be possible to overwrite the content-type with any value in context.call but it seems like we overlooked the case when there shouldn't be any content-type headers.

Can you try passing "" as content-type in context.call and see if it works for the endpoint you are calling?

In the meantime, we will look into addressing this.