如何让Uri.EscapeDataString符合RFC 3986 [英] How to get Uri.EscapeDataString to comply with RFC 3986

问题描述

Uri类默认为RFC 2396.对于OpenID和OAuth，我需要符合RFC 3986的Uri转义。

The Uri class defaults to RFC 2396. For OpenID and OAuth, I need Uri escaping consistent with RFC 3986.

从 System.Uri类文档：

默认情况下，URI中的任何保留字符都会根据RFC 2396进行转义。如果启用了国际资源标识符或国际域名解析，则会发生此行为，在这种情况下，URI中的保留字符将按照RFC 3986和RFC 3987。

By default, any reserved characters in the URI are escaped in accordance with RFC 2396. This behavior changes if International Resource Identifiers or International Domain Name parsing is enabled in which case reserved characters in the URI are escaped in accordance with RFC 3986 and RFC 3987.

该文档还指出，激活此IRI模式，从而启用RFC 3986行为意味着添加一个uri部分元素到machine.config，这到你的app / web.config文件：

The documentation also states that activating this IRI mode and thus the RFC 3986 behavior means adding a uri section element to machine.config and this to your app/web.config file:

<configuration>
  <uri>
  <idn enabled="All" />
  <iriParsing enabled="true" />
  </uri>
</configuration>

但是无论这是否存在于.config文件中，我得到相同的-3986）转义.NET 3.5 SP1应用程序的行为。 我还需要做些什么才能获得 Uri.EscapeDataString 使用RFC 3986规则？（具体来说，转义所定义的保留字符那个RFC）

But whether this is present in the .config file or not, I'm getting the same (non-3986) escaping behavior for a .NET 3.5 SP1 app. What else do I need to do to get Uri.EscapeDataString to use the RFC 3986 rules? (specifically, to escape the reserved characters as defined in that RFC)

推荐答案

不能让Uri.EscapeDataString承担RFC 3986的行为，我写了自己的RFC 3986符合转义方法。它利用Uri.EscapeDataString，然后升级转义为符合RFC 3986。

Having not been able to get Uri.EscapeDataString to take on RFC 3986 behavior, I wrote my own RFC 3986 compliant escaping method. It leverages Uri.EscapeDataString, and then 'upgrades' the escaping to RFC 3986 compliance.

/// <summary>
/// The set of characters that are unreserved in RFC 2396 but are NOT unreserved in RFC 3986.
/// </summary>
private static readonly string[] UriRfc3986CharsToEscape = new[] { "!", "*", "'", "(", ")" };

/// <summary>
/// Escapes a string according to the URI data string rules given in RFC 3986.
/// </summary>
/// <param name="value">The value to escape.</param>
/// <returns>The escaped value.</returns>
/// <remarks>
/// The <see cref="Uri.EscapeDataString"/> method is <i>supposed</i> to take on
/// RFC 3986 behavior if certain elements are present in a .config file.  Even if this
/// actually worked (which in my experiments it <i>doesn't</i>), we can't rely on every
/// host actually having this configuration element present.
/// </remarks>
internal static string EscapeUriDataStringRfc3986(string value) {
    // Start with RFC 2396 escaping by calling the .NET method to do the work.
    // This MAY sometimes exhibit RFC 3986 behavior (according to the documentation).
    // If it does, the escaping we do that follows it will be a no-op since the
    // characters we search for to replace can't possibly exist in the string.
    StringBuilder escaped = new StringBuilder(Uri.EscapeDataString(value));

    // Upgrade the escaping to RFC 3986, if necessary.
    for (int i = 0; i < UriRfc3986CharsToEscape.Length; i++) {
        escaped.Replace(UriRfc3986CharsToEscape[i], Uri.HexEscape(UriRfc3986CharsToEscape[i][0]));
    }

    // Return the fully-RFC3986-escaped string.
    return escaped.ToString();
}

这篇关于如何让Uri.EscapeDataString符合RFC 3986的文章就介绍到这了，希望我们推荐的答案对大家有所帮助，也希望大家多多支持IT屋！