title: Confusions about "Authorization: Bearer JWT_ACCESS_TOKEN"
body: <p>I am a beginner using <code>jsonwebtoken</code> to authenticate a user in my node.js web app. I signed a jwt token in <code>app.post('/login')</code> using <code>jwt.sign()</code> and when i try to access/ verify it in <code>app.get('/dashboard')</code> using <code>req.headers['authorization'].split(' ').[1]</code> it gives null or <code>undefined</code> as there is no authorization header in <code>console.log(req.headers)</code>.</p>
  <p>But it can be access or verify in postman as there i set auth type to <code>bearer &lt;token&gt;</code> due to which number of headers increment by 1 that is <code>authorization: bearer &lt;token&gt;</code>.</p>
  <p>Then i store the token in cookie using <code>res.cookie('token', accessToken)</code> and i can access it in my routes without postman.</p>
  <p>keeping in view above scenario i have following confusions:</p>
  <ul>
  <li>Where else can i store <code>jwt token</code> to access in my browser? and which is most secure store to access <code>jwt token</code> in browser?</li>
  <li>Why there is no <code>authorization: bearer &lt;token&gt;</code> header in my browser??</li>
  <li>Can i add <code>authorization: bearer &lt;token&gt;</code> header manually to access the token in my browser? if yes...how?</li>
  <li>If my app use <code>https</code> instead <code>http</code> protocol then will it be same situation of no <code>authorization: bearer &lt;token&gt;</code> header in browser?</li>
  </ul>
  <p>I googled it but cant conclude. please help....!</p>