Enkoder Script

Enkoder script is a convenient way to hide links and e-mail addresses from automated harvesting, while allowing people to use the links and to copy URL or mailto link information. Enkoder algorithm protects this link information by encrypting it in JavaScript code.

This Enkoder form was used for encrypting the test mailto link.

Test Enkoder Links

In normal operation, Enkoder script displays the specified link text and presents the encrypted URL or mailto link information when activated or copied. It is, however, at least occasionally subject to the GPC JS execution bug. Scripts affected by this bug generate their output into the source HTML of the page when the page is opened, saved, previewed, or edited in GPC. The following two links encrypted by Enkoder are the results of testing the stability of the associated JS code. This actual page has been "published" immediately after the scripts were pasted in the main field, to ensure that no further degradation could occur.

  • both of the following links originally Enkoded one copy of a dummy "mailto:user@example.com" link
  • below is an example of what happens to an Enkoded link affected by the GPC JS execution bug (note the multiple copies of this link created by GPC after this page was edited, opened, and saved several times)
    Dummy mailto linkDummy mailto link
  • below is an example of a stable Enkoded link—pasted into HTML and immediately published (no editing, no preview)

The latter procedure also has been successfully used to create the Enkoded e-mail link for GPX-Files contact information page.

GPC JS Bugs: Screenshots

The following two screenshots illustrate the effects of both the GPC JS execution and uneditable page bugs on a test Enkoder GooglePage as displayed in GPC using Firefox 1.5.0.4. The "before" screenshot on the left shows the page as-created, the "after" shot on the right is the same page with effects of both GPC JS bugs.

Enkoder Page Screenshot Before GPC JS Bugs Enkoder Page Screenshot After GPC JS Bugs

Between the "before" and "after" screenshots, the following procedure was performed:

  • page created as seen in the "before" screenshot
  • page saved (not published) in GPC
  • "Back To Page Manager" link selected in GPC
  • page immediately re-opened for editing from the GPC "Page Manager"
  • page displayed by GPC as seen in the "after" screenshot

The two screenshots show the effects of both JS bugs in GPC:

  • The footer field, which contains JS code for Google Analytics, has become uneditable in the "after" screenshot.
  • And while the JS Enkoded links are not displayed on the "before" page view, they do appear on the "after" page view (or rather the corresponding JS code output does).

Top