Microsoft Knowledge Base Email Alertz

KBAlertz.com: FIX: Error message when you visit an ASP.NET 2.0-based Web page: HttpException (0x80004005): '/HandlerTest/WebForm1.aspx/a:b' is not a valid virtual path

Receive Microsoft Knowledge Base articles by E-Mail?

Every night we scan the Microsoft Knowledge Base. If technologies you're interested in are updated, we'll send you an e-mail. You only get one e-mail a day, and only when new articles are added.

Click here to create a
FREE account
Already have an account?
[Click here to Login]

Search KbAlertz

Advanced Search

Webmasters
Put kbAlertz on your website.
[ Click Here for more! ]





ASP.NET 2.0 Web Hosting with SQL 2005: Click Here!
Discount ASP.NET Hosting


Bug Tracking Software
For bug tracking software or defect tracking software or issue tracking software, visit Axosoft.


Community Site



We Send hundreds of thousands of emails using ASP.NET Email



Expert Web Design & Graphic Design
Design44.com




Mentioned In








Microsoft Knowledge Base Article

This article contents is Microsoft Copyrighted material.
©2005-©2007 Microsoft Corporation. All rights reserved. Terms of Use | Trademarks




FIX: Error message when you try to visit an ASP.NET 2.0-based Web page: "HttpException (0x80004005): '/HandlerTest/WebForm1.aspx/a:b' is not a valid virtual path"

Retired KB ArticleThis article was written about products for which Microsoft no longer offers support. Therefore, this article is offered "as is" and will no longer be updated.
Article ID:932552
Last Review:November 12, 2007
Revision:2.2
Important This article contains information about how to modify the registry. Make sure that you back up the registry before you modify it. Make sure that you know how to restore the registry if a problem occurs. For more information about how to back up, restore, and modify the registry, click the following article number to view the article in the Microsoft Knowledge Base:
256986 (http://kbalertz.com/Feedback.aspx?kbNumber=256986/) Description of the Microsoft Windows registry
On This Page

SYMPTOMS

When you try to visit a Microsoft ASP.NET 2.0-based Web page, you may receive an error message that resembles the following:
HttpException (0x80004005): '/HandlerTest/WebForm1.aspx/a:b' is not a valid virtual path.
This problem occurs if the virtual path in the URL contains one of the following symbols:
•Colon (:)
•Asterisk (*)

For example, this problem occurs when you try to visit one of the following URLs:
• http://www.adventure:works.com/test.aspx
•http://www.adventure*works.com/test.aspx
Note This problem occurs even if you use the method that is described in Microsoft Knowledge Base article 826437 to set the value of the following registry subkey to 1:
HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\ASP.NET VerificationCompatibility

Back to the top

CAUSE

This problem occurs because of a change in ASP.NET 2.0. This change causes ASP.NET 2.0 to explicitly check any symbols in the virtual path in the URL when ASP.NET 2.0 validates the URL.

Back to the top

RESOLUTION

Hotfix information

A supported hotfix is now available from Microsoft. However, it is intended to correct only the problem that is described in this article. Apply it only to systems that are experiencing this specific problem. This hotfix may receive additional testing. Therefore, if you are not severely affected by this problem, we recommend that you wait for the next Microsoft .NET Framework service pack that contains this hotfix.

To resolve this problem immediately, contact Microsoft Customer Support Services to obtain the hotfix. For a complete list of Microsoft Customer Support Services telephone numbers and information about support costs, visit the following Microsoft Web site:
http://support.microsoft.com/contactus/?ws=support (http://support.microsoft.com/contactus/?ws=support)
Note In special cases, charges that are ordinarily incurred for support calls may be canceled if a Microsoft Support Professional determines that a specific update will resolve your problem. The usual support costs will apply to additional support questions and issues that do not qualify for the specific update in question.

Prerequisites

You must have Microsoft .NET Framework 2.0 installed to apply this hotfix.

Restart requirement

You do not have to restart the computer after you apply this hotfix.

Hotfix replacement information

This hotfix does not replace any other hotfixes.

File information

The English version of this hotfix has the file attributes (or later file attributes) that are listed in the following table. The dates and times for these files are listed in Coordinated Universal Time (UTC). When you view the file information, it is converted to local time. To find the difference between UTC and local time, use the Time Zone tab in the Date and Time item in Control Panel.
The .NET Framework 2.0, x86-based versions
File nameFile versionFile sizeDateTimePlatform
Aspnet_wp.exe2.0.50727.80432,60012-Feb-200719:20x86
System.web.dll2.0.50727.8045,156,86412-Feb-200719:20x86
Webengine.dll2.0.50727.804406,01612-Feb-200719:20x86
The .NET Framework 2.0, x64-based versions
File nameFile versionFile sizeDateTimePlatform
Aspnet_wp.exe2.0.50727.80444,37612-Feb-200714:33x64
System.web.dll2.0.50727.8045,087,23212-Feb-200714:33x64
Webengine.dll2.0.50727.804710,14412-Feb-200711:23x64
The .NET Framework 2.0, Itanium-based versions
File nameFile versionFile sizeDateTimePlatform
Aspnet_wp.exe2.0.50727.80483,28812-Feb-200715:17IA-64
System.web.dll2.0.50727.8044,710,40012-Feb-200715:17IA-64
Webengine.dll2.0.50727.8041,181,69612-Feb-200711:25IA-64

Registry information

Warning Serious problems might occur if you modify the registry incorrectly by using Registry Editor or by using another method. These problems might require that you reinstall the operating system. Microsoft cannot guarantee that these problems can be solved. Modify the registry at your own risk.

After you apply this hotfix, you must enable it by setting the value of the VerificationCompatibility entry of the following registry subkey to 1:
HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\ASP.NET
DWord Value Name: VerificationCompatibility
Value Data: 1
Important If you enable this hotfix, ASP.NET will not automatically check whether a URL contains special symbols. Therefore, you increase the attack surface of the application. You should not enable this hotfix unless the application requires that you take this action. If you enable this hotfix, you must manually make sure that URLs are handled correctly.

Back to the top

STATUS

Microsoft has confirmed that this is a problem in the Microsoft products that are listed in the "Applies to" section.

Back to the top

MORE INFORMATION

For more information about software update terminology, click the following article number to view the article in the Microsoft Knowledge Base:
824684 (http://kbalertz.com/Feedback.aspx?kbNumber=824684/) Description of the standard terminology that is used to describe Microsoft software updates

Back to the top


APPLIES TO
•Microsoft ASP.NET 2.0

Back to the top

Keywords: 
kbexpertiseadvanced kbhotfixserver kbqfe kbpubtypekc KB932552

Back to the top

       

Community Feedback System

Very often, it takes hours to solve a problem. Very often, you've looked high and low, and have tried a lot of solutions. When you finally found it, chances are, it was because someone else helped you. Here's your chance to give back. Use our community feedback tool to let others know what worked for you and what didn't.

Please also understand that the community feedback system is not warranted to be correct, it's simply a system that we've built to let people try and help each other. If something in a feedback response doesn't make sense to you, or you're not comfortable making changes that the feedback talks about (like registry edits), please consult a professional.

Thank you for using kbAlertz.com Feedback System.

-- Scott Cate

Be the first to leave feedback, to help others about this knowledge base article.

(Optional) Name

(Optional) Public URL Or Email

Comments
No HTML -- Text Only Please