title: HTTP trigger azure function won't bind route parameter with encoded slashes
body: <p>I've created an Azure C# HTTP triggered function with a route url: <code>subscriptions/{token}/t</code>. It works fine for urls such as <code>subscriptions/blah/t</code> but it fails with a <code>404</code> for parameters that contain encoded slashes: <code>subscriptions/blah%2fblah/t</code>. Any way around this ?</p>
  
  <p>Before we get into debates, <code>{token}</code> is a URL encoded Base64 string which will naturally contain slashes.</p>