title: URL Fragment and 302 redirects
body: <p>It's well known that the URL fragment (the part after the <code>#</code>) is not sent to the server. </p>
  
  <p>I do wonder though how fragments work when a server redirect (via HTTP status 302 and <code>Location:</code> header) is involved.</p>
  
  <p>My question is really two-fold:</p>
  
  <ol>
  <li><p>If the original URL had a fragment (<code>/original.php#foo</code>), and a redirect is made to <code>/new.php</code>, does the fragment part of the original URL simply get lost? Or does it sometimes get applied to the new URL? <br>Will the new URL ever be <code>/new.php#foo</code> in this case?</p></li>
  <li><p>Regardless of the original URL, if the server redirects to a new URL with a fragment (<code>/new.php#foo</code>), will the fragment get "honored"? Or does the server really have no business interfering with the fragment at all -- and will the browser therefore ignore it by simply going to <code>/new.php</code>??</p></li>
  </ol>