IIS和ASP.NET(MVC)has some glitches在路径中使用%-encoding的URL时(不是查询字符串;查询字符串很好)。我怎么能绕过这个?即,我如何获得所请求的实际URL?
例如,如果我导航到/x%3Fa%3Db
和(单独)导航到/x?a=b
- 他们都会将.Request.Url
报告为/x?a=b
- 因为编码数据路径报告错误。
答案 0 :(得分:21)
我解决这个问题的方法是查看底层服务器变量; URL
变量包含已解码的值; QUERY_STRING
变量包含仍然编码的查询。我们不能只在URL
部分调用 encode ,因为它还包含原始形式的orignal /
等 - 如果我们盲目编码整个事物,我们将会得到不需要的%2f
值;然而,可以将它拉开并发现有问题的案例:
private static readonly Regex simpleUrlPath = new Regex("^[-a-zA-Z0-9_/]*$", RegexOptions.Compiled);
private static readonly char[] segmentsSplitChars = { '/' };
// ^^^ avoids lots of gen-0 arrays being created when calling .Split
public static Uri GetRealUrl(this HttpRequest request)
{
if (request == null) throw new ArgumentNullException("request");
var baseUri = request.Url; // use this primarily to avoid needing to process the protocol / authority
try
{
var vars = request.ServerVariables;
var url = vars["URL"];
if (string.IsNullOrEmpty(url) || simpleUrlPath.IsMatch(url)) return baseUri; // nothing to do - looks simple enough even for IIS
var query = vars["QUERY_STRING"];
// here's the thing: url contains *decoded* values; query contains *encoded* values
// loop over the segments, encoding each separately
var sb = new StringBuilder(url.Length * 2); // allow double to be pessimistic; we already expect trouble
var segments = url.Split(segmentsSplitChars);
foreach (var segment in segments)
{
if (segment.Length == 0)
{
if(sb.Length != 0) sb.Append('/');
}
else if (simpleUrlPath.IsMatch(segment))
{
sb.Append('/').Append(segment);
}
else
{
sb.Append('/').Append(HttpUtility.UrlEncode(segment));
}
}
if (!string.IsNullOrEmpty(query)) sb.Append('?').Append(query); // query is fine; nothing needing
return new Uri(baseUri, sb.ToString());
}
catch (Exception ex)
{ // if something unexpected happens, default to the broken ASP.NET handling
GlobalApplication.LogException(ex);
return baseUri;
}
}