annevk: given that for 3xx response with no Location header but with a response body, the Fetch spec doesn’t explicitly prohibit UAs from processing the response body, and given that there’s also nothing in HTML that prohibits it either, I guess that means UAs can choose to do whichever they want with it (process it or not)?

…and lacking any spec requirements around it, it’s not something that can be expected to necessarily behave interoperably?

I have a Stack-Overflow-like question. What's a way to rewrite the following whereby "example.unlikely" as input doesn't result in a false-negative? I guess one could hash the input somehow, but that seems really gross?

function parseHost(input) {
  dummy = new URL("http://example.unlikely");
  dummy.host = input;
  if (dummy.host !== "example.unlikely")
    return dummy.host;
  return null;
}

function parseHost(input) {
  const false_host = `${uuid()}.unguessable`;
  dummy = new URL("http://${false_host}");
  dummy.host = input;
  if (dummy.host !== false_host)
    return dummy.host;
  return null;
}

?

does anyone know what part spec (webidl?) mentions if functions should be async/sync? ie:

const asyncFn = (async function() {}).constructor

fetch instanceof asyncFn // false

thanks!