Coffeehouse Thread

7 posts

Microsoft.com broken

Back to Forum: Coffeehouse
  • User profile image
    MattShepherd

    http://register.microsoft.com/contactus30/contactus.asp?domain=windefault

    The contact us page on MS seems to be missing a closing quote Smiley

    Anyone at MS want to pass this onto the correct people?

  • User profile image
    Steve411

    Sent.

  • User profile image
    W3bbo

    MattShepherd wrote:
    http://register.microsoft.com/contactus30/contactus.asp?domain=windefault

    The contact us page on MS seems to be missing a closing quote

    Anyone at MS want to pass this onto the correct people?


    Why are they still using ASP3 anyway?

    And more importantly... why is ASP Script Debugging enabled?

  • User profile image
    ZippyV

    W3bbo wrote:
    Why are they still using ASP3 anyway?

    And more importantly... why is ASP Script Debugging enabled?
    Looks like you don't know how big Microsoft.com really is.

  • User profile image
    Steve411

    Some guy or girl is too lazy to update the pages, or is fired by now. Who knows.

  • User profile image
    dnrfan

    . wrote:
    And more importantly... why is ASP Script Debugging enabled?

    Maybe they had it on during the 64Bit transition, and forgot to disable it, once everything worked.

  • User profile image
    Maurits

    W3bbo wrote:

    Why are they still using ASP3 anyway?


    If you use the Session object to hold user state, the transition from ASP3 to ASP.NET is a bear.

    W3bbo wrote:

    and more importantly... why is ASP Script Debugging enabled?


    Actually "echo errors to client" is enabled - useful for troubleshooting errors in new code.  Turning it off does seal a mild kind of "information disclosure" but sometimes the error troubleshooting is so valuable that it's almost worth leaving it on.

    Ideally there'd be a way to specify some kind of authorization method to be able to show errors only to certain developers/testers, and not to the general public.

Comments closed

Comments have been closed since this content was published more than 30 days ago, but if you'd like to continue the conversation, please create a new thread in our Forums, or Contact Us and let us know.