Article ID: 190893 - Last Review: May 11, 2006 - Revision: 3.0

BUG: Registry Patterns Ignored for Pluggable Namespace Handlers

View products that this article applies to.

This article was previously published under Q190893

SYMPTOMS

Microsoft Internet Explorer, versions 4.0 and later, ignore the pattern keys set in the registry when determining which permanent pluggable namespace handlers to invoke.

Back to the top

Create a temporary pluggable namespace handler instead of a permanent namespace handler. Use IInternetSession::RegisterNameSpace and IInternetSession::UnregisterNameSpace to register and unregister a temporary pluggable namespace handler, respectively.

Back to the top

STATUS

Microsoft has confirmed that this is a bug in the Microsoft products that are listed at the beginning of this article.

Back to the top

MORE INFORMATION

Pluggable namespace handlers currently do not recognize the pattern strings set in the registry. This bug causes the namespace handler to be called for all protocol calls and not just the ones that match the listed patterns. As an example of what the correct behavior should be, a namespace handler entry in the registry as follows:

HKEY_CLASSES_ROOT\PROTOCOLS\Name-Space Handler\http\myserv-Handler
   CLSID = {..}
   Pattern1 = "myserver"

should only be called for URLs that begin with http://myserver/ and the default HTTP pluggable protocol handler should be called for all other HTTP URLs.

Back to the top

REFERENCES

For more information about developing Web-based solutions for Microsoft Internet Explorer, visit the following Microsoft Web sites:

http://msdn.microsoft.com/ie/ (http://msdn.microsoft.com/ie/)

http://support.microsoft.com/iep (http://support.microsoft.com/iep)

Back to the top

APPLIES TO

Microsoft Internet Explorer 4.0 128-Bit Edition
Microsoft Internet Explorer 4.01 Service Pack 2
Microsoft Internet Explorer 4.01 Service Pack 1
Microsoft Internet Explorer 5.0
Microsoft Internet Explorer 5.5

Back to the top

kbbug kbmoniker kbpending kburl KB190893

Back to the top

Retired KB Content Disclaimer

This 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.

Back to the top