title: basic HTTP authentication on subsequent requests
body: <p>The image below depicts basic HTTP authentication. The client requests <code>/family</code> resource and it is asked to identify itself. It does and now it can access the <code>/family</code>. The client then also asks for <code>/family/photos/kids</code> resource which is in the family realm. </p>
  
  <p>The client already identified itself for <code>/family</code> resource, but not also for <code>/family/photos/kids</code>. They are in the same realm, but the server doesn't know that the same client issued a request. Or does it? How does the server know that this particular client is also allowed to access <code>/family/photos/kids</code> on subsequent request? Is the password and username send on every request after the user has authenticated? Is the client asked for via pop-up for every request he/she makes? Are cookies set upon first authentication?</p>
  
  <p><a href="https://i.stack.imgur.com/o6FDL.png" rel="noreferrer"><img src="https://i.stack.imgur.com/o6FDL.png" alt="enter image description here"></a></p>