Home > AXS Visitor Tracking > Help > 1510

Problem URL's containing the wysiwyg:// protocol

Some visits to your site may use the wysiwyg:// protocol in the referring URL.

These visits will appear in the database listings as:

A visitor from scfwpr03.sc.intel.com (
arrived from wysiwyg://DYNA/http://www.xav.com/perl/
and visited www.xav.com/perl/lib/Pod/perlobj.html

Within the graph listings, AXS may get confused about whether to treat these wysiwyg:// URL's as local or remote URL's. You may get duplicate entries in your graph listings since some contain leading wysiywg:// protocols and others do not.

Work-Arounds in AXS

You can suppress these URL's by customizing the %Maps hash in the ax.pl or ax.cgi file. The default hash looks like this:

my %Maps = (
	'http://xav.com/'     => 'http://www.xav.com/',
	'http://ftp.xav.com/' => 'http://www.xav.com/',

Just add a new entry to strip the leading portion of this protocol:

my %Maps = (
	'http://xav.com/'     => 'http://www.xav.com/',
	'http://ftp.xav.com/' => 'http://www.xav.com/',
	'^wysiwyg://.*?/http://' => 'http://',

Making the above change to the %Maps hash will clean up all incoming data, but it will not clean up data that has already been logged.


From what I've read, the wysiwyg:// protocol is used by early versions of Netscape for viewing cached copies of Javascript-generated windows, and for Print and Print Preview windows. The URL wysiwyg://DYNA/http://www.xav.com/perl/ might refer to a cached copy of a Netscape Javascript-generated window named "DYNA" which contains the contents of http://www.xav.com/perl/.

The protocol does not seemed to be used in newer versions of Netscape, and does not seem to be used in other browsers.

From http://developer.netscape.com/support/faqs/champions/javascript.html#2-8

2.8: Why do I sometimes see a URL beginning with wysiwyg?

(What you see is what you get!)

While working with client-side JavaScript code, one might see URL's in the format: wysiwyg:/0/http://www.myserver.com/document.html. These are internal references that are displayed in the location field and are not troublesome in any way to either users or developers. The "0" in the example is an internal document id, not a controllable parameter.

From http://web-wise-wizard.com/internet-web-www/internet-rough-guide-url-protocol-urls.html

"When working with client-side JavaScript and using a Netscape browser (v3 or earlier), you may occasionally see a URL that has the wysiwyg: protocol and a document ID number preceding the normal URL. These are internal references that are displayed in the location field and are not troublesome in any way. The "123" in the example is the internal document ID number and this is not a controllable parameter.


The term WYSIWYG is an acronym for "what you see is what you get" and the wysiwyg: protocol preceding the URL denotes that JavaScript has loaded the page from the browser's cache. This only appears to occur when manipulating HTML documents that have previously been generated by JavaScript. So for example, whenever you resize an HTML page that has been generated by JavaScript, you will see this behavior.

The 'wysiwyg:' protocol is mentioned in the JavaScript protocols section of the JavaScript Reference v1.2 where it is used in conjunction with the view-source: protocol (i.e. view-source:wysiwyg:). We cannot find any further information regarding it and suspect that once again, it is used internally or is depreciated. Our tests have not revealed any advantageous use of it and in many cases it has stopped the view-source protocol from operating correctly so our advice is to leave it alone altogether, that is unless you know something about it that we don't. If you do know something about it that we don't then it would be great to hear from you."

    "Problem URL's containing the wysiwyg:// protocol"