A potentially dangerous Request.QueryString value was detected

Ask a Question related to ASP.NET Security, Design and Development.

  1. #1

    Default Re: A potentially dangerous Request.QueryString value was detected

    Hi,

    The querystring contains a custom error message while we are trapping
    any duplicate record entry. The exact string is
    as given below:

    "Adding the record failed.<br>Error Code: 2627<br>Error Description:
    Duplicate value."

    The same thing works find on development m/c whereas on most of the m/c
    its throwing the said error message.

    Hope this will be of any use.

    regards

    Vinay

    *** Sent via Developersdex [url]http://www.developersdex.com[/url] ***
    Don't just participate in USENET...get rewarded for it!
    Vinay Panchal Guest

  2. Similar Questions and Discussions

    1. What is the difference between REQUEST and REQUEST.QUERYSTRING?
      What is the difference between these two statements? They seem to do the same thing... response.write(request("variable")) ...
    2. Getting "A potentially Dangerous Request.Cookies Value" error
      Hello, I recently upgraded from VS.NET 2002 to VS.NET 2003. Since I did that, I receive the following error from time to time: A potentially...
    3. A potentially dangerous querystring ... [ValidateRequest]
      All, When i use .net FRamework 1.1, for my web application, i get an error saying "A potentially dangerous querystring was detected from the...
    4. Confused about a REQUEST.FORM and a REQUEST.QUERYSTRING
      This is snipit of code, supplied by PayPal with explanation about what has to be done to access their back end. I am confused because they first...
    5. difference bet. request.querystring and Request.Params
      request.params for asp.net is the httprequest object, and this method gets a combined collection of querystring, cookies, form and servervars...
  3. #2

    Default Re: A potentially dangerous Request.QueryString value was detected

    It's likely that < and > are disallowed in the query string (to prevent
    someone injecting javascript code in the query string that could then be
    executed). I don't know if this an ASP.NET setting or if a tool such as
    URLSCAN is in use...

    for now you may want to adjust this setting but generally it's preferable to
    avoid passing such things in the querystring. Yo'ull find some details at
    [url]http://www.microsoft.com/technet/treeview/default.asp?url=/technet/security/[/url]
    news/crssite.asp and especially a link to
    [url]http://support.microsoft.com/default.aspx?scid=kb;en-us;Q252985&sd=tech[/url]


    --

    "Vinay Panchal" <vinay@vbsoftindia.com> a écrit dans le message de news:
    #5DR45eRDHA.1324@TK2MSFTNGP11.phx.gbl...
    > Hi,
    >
    > The querystring contains a custom error message while we are trapping
    > any duplicate record entry. The exact string is
    > as given below:
    >
    > "Adding the record failed.<br>Error Code: 2627<br>Error Description:
    > Duplicate value."
    >
    > The same thing works find on development m/c whereas on most of the m/c
    > its throwing the said error message.
    >
    > Hope this will be of any use.
    >
    > regards
    >
    > Vinay
    >
    > *** Sent via Developersdex [url]http://www.developersdex.com[/url] ***
    > Don't just participate in USENET...get rewarded for it!
    Patrice Scribe Guest

  4. #3

    Default Re: A potentially dangerous Request.QueryString value was detected



    Thanks. i will try removing the <br> tags and let u know if it works.




    *** Sent via Developersdex [url]http://www.developersdex.com[/url] ***
    Don't just participate in USENET...get rewarded for it!
    Vinay Panchal Guest

  5. #4

    Default Re: A potentially dangerous Request.QueryString value was detected

    "Vinay Panchal" <vinay@vbsoftindia.com> wrote in message
    news:%237UQ1upRDHA.2196@TK2MSFTNGP11.phx.gbl...
    >
    > Thanks everybody for the help.
    > It works after removing the script tags from the querystring parameter.
    >
    > Still if anybody can find any other solution to this, its always welcome
    To me this feature is an MS overreaction on security

    <?xml version="1.0"?>
    <configuration>
    <system.web>
    <pages validateRequest="false"/>
    etc

    --
    compatible web farm Session replacement for Asp and Asp.Net
    [url]http://www.nieropwebconsult.nl/asp_session_manager.htm[/url]

    > regards
    >
    > Vinay
    >
    >
    > *** Sent via Developersdex [url]http://www.developersdex.com[/url] ***
    > Don't just participate in USENET...get rewarded for it!
    Egbert Nierop \(MVP for IIS\) Guest

Posting Permissions

  • You may not post new threads
  • You may post replies
  • You may not post attachments
  • You may not edit your posts

1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19 20 21 22 23 24 25 26 27 28 29 30 31 32 33 34 35 36 37 38 39 40 41 42 43 44 45 46 47 48 49 50 51 52 53 54 55 56 57 58 59 60 61 62 63 64 65 66 67 68 69 70 71 72 73 74 75 76 77 78 79 80 81 82 83 84 85 86 87 88 89 90 91 92 93 94 95 96 97 98 99 100 101 102 103 104 105 106 107 108 109 110 111 112 113 114 115 116 117 118 119 120 121 122 123 124 125 126 127 128 129 130 131 132 133 134 135 136 137 138 139