title: does Request.Querystring automatically url decode a string?
body: <p>I'm working with a page where I have a url like:<br>
  /directory/company/manufacturer</p>
  
  <p>Using some re-write rules this gets re-written</p>
  
  <p>testing with /directory/company/dunkin%26donuts/</p>
  
  <p>Some manufacturers have an ampersand in their name. So I thought I could just replace the ampersand with <code>%26</code>. However, when I debug the code and hover over <code>Request.QueryString</code> it shows me <code>{qq=company&amp;manf=dunkin&amp;donuts&amp;cond=}</code> and <code>Request.QueryString["manf"]</code> gives me 'dunkin'</p>
  
  <p>If I use <code>%24</code> ($) instead of ampersand, hovering over <code>Request.QueryString</code> gives me
  <code>{qs=company&amp;manf=dunkin%24donuts&amp;cond=}</code> and <code>Request.QueryString["manf"]</code> gives me 'dunkin$donuts'</p>
  
  <p>I don't understand the different behavior here. Why does it seem as though the url-encoded value for an ampersand gets decoded before you actually request a specific key, but another url-encoded character, like a dollar sign, only gets decoded after you actually request that specific key?</p>
  
  <p>Is this a recent change? I always thought <code>Request.QueryString[key]</code> returned the actual text without decoding it first. Or does it have something to do with url re-writes?</p>