title: Web Api 2 routing issue with special characters in URL
body: <p>In the middle of developing a Web Api 2 REST service, we have discovered a routing problem. The endpoint is as follows:</p>
  
  <p>.../{email}/...</p>
  
  <p>The problem is that the email could contain special characters such as '+', which results in a 404 resource not found.</p>
  
  <p>We would really like for the user of the service, to be able to specify the email in the URL. But since the email also legally can contain an '&amp;', this can't just be moved to an URL parameter. How would we go about solving this?</p>
  
  <p>Regards
  Frederik</p>