title: Printing simple text using fetch and await. Why do I need more than one await inside an async function?
body: <p>I'm trying to do webcrawling using fetch on React Native. This is what I'm doing:</p>
  
  <pre><code>  const response = fetch(
          url,
          {
              body          : post_data ? post_data : undefined, // must match 'Content-Type' header
              cache         : 'no-cache', // *default, no-cache, reload, force-cache, only-if-cached
              headers       : headers,
              method        : post_data ? 'POST' : 'GET', // *GET, POST, PUT, DELETE, etc.
              redirect      : redirect ? 'follow' : 'manual', // *manual, follow, error. TODO: is manual the right keyword?
              referrer      : 'no-referrer', // *client, no-referrer
          }
      );
  
      const http   = await response;
      const header = http.headers;
      const html   = http.text();
  
      console.log(html);
  </code></pre>
  
  <p>When I print <code>header</code>, I can see the headers. When I print <code>html</code>, this is what I see:</p>
  
  <pre><code>{ _40: 0, _65: 0, _55: null, _72: null }
  </code></pre>
  
  <p>What am I possibly doing wrong? I thought one await was necessary, but if I change to:</p>
  
  <pre><code>const http   = await response;
  const header = await http.headers;
  const html   = await http.text();
  
  console.log(html);
  </code></pre>
  
  <p>then I can see the HTML. But as I've read, <a href="https://developer.mozilla.org/en-US/docs/Web/JavaScript/Reference/Operators/await" rel="nofollow noreferrer">await makes the execution pause and resolves the Promise</a>. So why should I need the two extra awaits below await response?</p>