Question

我正在开发一个App.net的项目,并且有加密方法。当它被用于加密时,它就归还了含有诸如+等一些果园的插图,而且由于在我的询问中使用了其回归的数值,即需要拆除这些果园。

页: 1

http://localhost/Cpanel/CompanyInfo/Hotels/EditHotel/VKWbk+G9F6E=

Error : HTTP Error 404.11 - Not Found The request filtering module is configured to deny a request that contains a double escape sequence.

http://localhost/Cpanel/CompanyInfo/Hotels/EditHotel/bprrmsZ6atI=

著作

这是我的加密方法:

 public static string EncryptString(string Message)
        {
            string Passphrase = System.Configuration.ConfigurationSettings.AppSettings["CryptographyKey"];

            byte[] Results;
            System.Text.UTF8Encoding UTF8 = new System.Text.UTF8Encoding();

            //Hash the passphrase using MD5            
            MD5CryptoServiceProvider HashProvider = new MD5CryptoServiceProvider();
            byte[] TDESKey = HashProvider.ComputeHash(UTF8.GetBytes(Passphrase));

            TripleDESCryptoServiceProvider TDESAlgorithm = new TripleDESCryptoServiceProvider();
            TDESAlgorithm.Key = TDESKey;
            TDESAlgorithm.Mode = CipherMode.ECB;
            TDESAlgorithm.Padding = PaddingMode.PKCS7;

            byte[] DataToEncrypt = UTF8.GetBytes(Message);

            try
            {
                ICryptoTransform Encryptor = TDESAlgorithm.CreateEncryptor();
                Results = Encryptor.TransformFinalBlock(DataToEncrypt, 0, DataToEncrypt.Length);
            }
            finally
            {
                TDESAlgorithm.Clear();
                HashProvider.Clear();
            }

            return HttpUtility.HtmlEncode(Convert.ToBase64String(Results));
        }

如何做到这一点?

Answer 1

当你准备显示价值时,情况如下:

Server.UrlEncode(Variable)

然后通过询问。

在阅读时,对编码的使用方法如下:

Server.UrlDecode("QuerySting");

让我了解任何关切。

Answer 2

看来你的“加密”是一种基础64编码。第64基地只使用字母数字特性、+特性和平等=特性。平等性并不引起任何问题,只有“+”(在《国际仲裁裁决汇编》中被解释为空间)。你可以直截了当。将“+”改为“......,反之亦然”,由主控制人来做。

另一种做法(不需要修改法典)是允许在你的网站上重复使用。召集:

<system.webServer>
    <security>
        <requestFiltering allowDoubleEscaping="true"/>
    </security>
</system.webServer>

This will only work with IIS, not with ASP.NET Development Server. However, this imposes some security concerns. For details, here is a very god article covering this: http://www.hanselman.com/blog/ExperimentsInWackinessAllowingPercentsAnglebracketsAndOtherNaughtyThingsInTheASPNETIISRequestURL.aspx

友情链接