I don't think this is a bug. no-cors only supports content-types of application/x-www-form-urlencoded, multipart/form-data or text/plain.

[clasterA]

I don't think this is a bug. no-cors only supports content-types of application/x-www-form-urlencoded, multipart/form-data or text/plain.

[github-actions]

Would you be able to provide a reproduction? 🙏

More info

Why do I need to provide a reproduction?

Reproductions make it possible for us to triage and fix issues quickly with a relatively small team. It helps us discover the source of the problem, and also can reveal assumptions you or we might be making.

What will happen?

If you've provided a reproduction, we'll remove the label and try to reproduce the issue. If we can, we'll mark it as a bug and prioritize it based on its severity and how many people we think it might affect.

If needs reproduction labeled issues don't receive any substantial activity (e.g., new comments featuring a reproduction link), we'll close them. That's not because we don't care! At any point, feel free to comment with a reproduction and we'll reopen it.

How can I create a reproduction?

We have a couple of templates for starting with a minimal reproduction:

👉 https://stackblitz.com/github/nuxt/starter/tree/v3-stackblitz
👉 https://codesandbox.io/s/github/nuxt/starter/v3-codesandbox

A public GitHub repository is also perfect. 👌

Please ensure that the reproduction is as minimal as possible. See more details in our guide.

You might also find these other articles interesting and/or helpful:

• The Importance of Reproductions
• How to Generate a Minimal, Complete, and Verifiable Example

[danielroe]

Try this in your browser console:

fetch('https://jsonplaceholder.typicode.com/todos/1', {
  method: "GET",
  mode: "no-cors",
  headers: {
    "Content-Type": "text/plain",
    "Access-Control-Allow-Origin": "",
    "Access-Control-Allow-Methods": "GET,POST,OPTIONS",
    "Access-Control-Allow-Credentials": "",
    Authorization: `Bearer Bob`,
  }
}).then((result) => {
  console.log("data ", result);
})

Then inspect the request headers.

You can see that only a subset of headers is allowed/passed on. This is the Fetch specification, which is a browser API.

If useFetch differs from this, please provide a reproduction and I'll happily reopen.

[clasterA]

The problem with mode: "no-cors", is that it completely removes user-set header settings.
And it has nothing to do with the selected content type as you write in your comment in the previous ticket.

danielroe commented on Jan 30, 2023
I don't think this is a bug. no-cors only supports content-types of application/x-www-form-urlencoded,multipart/form-data or text/plain.

[danielroe]

Are you talking about the behaviour of the Fetch API or useFetch? Would you provide a reproduction that shows a bug here?

[danielroe]

See https://developer.mozilla.org/en-US/docs/Web/API/Fetch_API/Using_Fetch#supplying_request_options.