We are excited to announce that the IIS.NET Forums are moving to the new Microsoft Q&A experience. Learn more >

View Complete Thread
  • Re: A potentially dangerous Request.Path value was detected from the client (:)

    May 11, 2021 09:53 AM|samwu|LINK

    Hi mrbot,



    As per the ASCI encoding this url part

    2) dma:///45e6b900-8929-11d4-b772-0050da06bfb4/7bd350da-c9ee-4565-8000-2cbc18041961

    was converted as below.


    when 3rd URL is passed through IIS reverse proxy  %2F%2F%2F is getting replaced as %2F. That's resulting request URL as invalid

    is there a way where i can retain the encoding part of URL after;

    when passed through IIS reverse proxy ? Something like 

    You can try to use url rewriting. how do you generate such a complicated URL?

    Best regards,


    IIS.NET forums are moving to a new home on Microsoft Q&A, we encourage you to go to Microsoft Q&A for .NET for posting new questions and get involved today. Learn more >