locked
When should I use the 3.5SP1+ version of the workaround RRS feed

  • Question

  • User-465460119 posted

    Since ASP.Net 2.0, 3.0, 3.5 and 3.5SP1 all use the 2.0 CLR, how do I determine if I should use the CustomErrors.aspx page (with delay).  Is it based on the latest ASP.Net version installed, or does it depend on my web.config?

    If I have a classic ASP site (but it has the ASP.Net scriptmaps installed) should I use the static fix or the dynamic fix?

    Saturday, September 18, 2010 11:22 AM

Answers

  • User1172313662 posted

    Yes use the 2.0 version of the work around.

    • Marked as answer by Anonymous Thursday, October 7, 2021 12:00 AM
    Saturday, September 18, 2010 11:48 AM

All replies

  • User541108374 posted

    Hi,

    first of all check the control panel where you host your application. If still in doubt ask the helpdesk of your hosting company and make them aware too of the blog post of Scott Guthrie so that they can proactively put a message on some forum of their sites or send a mail to all people concerned: http://weblogs.asp.net/scottgu/archive/2010/09/18/important-asp-net-security-vulnerability.aspx.

    Grz, Kris. 

    Saturday, September 18, 2010 11:30 AM
  • User-465460119 posted

    This did not really answer the question.  I am here because of Scott's post, and needed a little clarification (and thought everyone else might benefit from the answer).  I have ASP.Net 3.5 SP1 installed on the machine, but my understanding is that it's not really a 3.5 SP1 site unless the web.config is configured to use the 3.5 compiler.  So, If I just have an empty site with no web.config BUT have the ASP.Net scriptmaps installed (pointed to the 2.0 dlls), I assume I use the error.htm version of the workaround.

    Saturday, September 18, 2010 11:45 AM
  • User1172313662 posted

    Yes use the 2.0 version of the work around.

    • Marked as answer by Anonymous Thursday, October 7, 2021 12:00 AM
    Saturday, September 18, 2010 11:48 AM
  • User-465460119 posted

    Thanks.

    Saturday, September 18, 2010 11:54 AM