URI segments, dots, REST, and a .NET bug

Originally Authored by Rodrigo de Casto

1. Resource is created by posting to URL: http://host/addresses. At this point, the resource name is passed in the payload and your service will correctly accept these trailing dots. For example, let's say we create an address named "home." So far, so good.
2. User tries to perform a REST operation on this resource. It could be something as simple as a GET on http://host/addresses/home. (dot included)
3. In the case you have a .NET client, the request will go out as http://host/addresses/home (no dot). Of course your server will return the wrong data or an error (like 404 - not found)
4. In case you have a non-.NET client, the request will go out correctly, but if your server is .NET-based, then you may have an issue. For instance, a WCF REST service will have this resource name parsed as "home" (no dots), which will also return the wrong data or an error.

MethodInfo getSyntax = typeof(UriParser).GetMethod("GetSyntax", System.Reflection.BindingFlags.Static | System.Reflection.BindingFlags.NonPublic);
FieldInfo flagsField = typeof(UriParser).GetField("m_Flags", System.Reflection.BindingFlags.Instance | System.Reflection.BindingFlags.NonPublic);
if (getSyntax != null && flagsField != null)
{
  foreach (string scheme in new[] { "http", "https" })
  {
      UriParser parser = (UriParser)getSyntax.Invoke(null, new object[] { scheme });
      if (parser != null)
      {
          int flagsValue = (int)flagsField.GetValue(parser);
          // Clear the CanonicalizeAsFilePath attribute
          if ((flagsValue & 0x1000000) != 0)
              flagsField.SetValue(parser, flagsValue & ~0x1000000);
      }
  }
}