title: HttpUtility.UrlEncode standard encoding vs specified encoding?
body: <p>What would the difference be between:</p>
  
  <pre><code>HttpUtility.UrlEncode("some string with é and β and stuff")
  HttpUtility.UrlEncode("some string with é and β and stuff", Encoding.UTF8)
  HttpUtility.UrlEncode( "some string with é and β and stuff", Encoding.Default )
  </code></pre>
  
  <p>result being:</p>
  
  <pre><code>some+string+with+%c3%a9+and+%ce%b2+and+stuff
  some+string+with+%c3%a9+and+%ce%b2+and+stuff
  some+string+with+%e9+and+%df+and+stuff
  </code></pre>
  
  <p>When testing, I get the same result for the first two, so can i safely assume that UTF8 is the default unless specified, or can that differ on different systems?</p>
  
  <p>I have seene examples of unicode escape sequences that looks like this:</p>
  
  <p>%u00e9 (é)</p>
  
  <p>Fairly certain that paypal sends that in their IPN-requests. Why doesn't .NET encode like that?</p>