Inserting an XHTML 1.0 compliant JavaScript block (xhtml10)

The -j junction option modifies HTML documents returned from junctioned servers by inserting a JavaScript block that sets a junction identification cookie on the browser interpreting the document. The default script is not compliant with XHTML 1.0 specifications.

To configure WebSEAL to insert a junction cookie JavaScript block that is compliant with XHTML 1.0 specifications (and HTML 4.01 specifications), add the -J option with the xhtml10 argument when creating the -j junction. For example (command line fragment):

pdadmin> server task instance-webseald-host create ... -j -J xhtml10 ... 

• The JavaScript inserted using this option may not execute if the Content-Type of the document it is inserted into is not text/html. This will typically not be a problem because most sites issue XHTML with Content-Type: text/html.
• The onfocus and xhtml10 arguments for the -J option are mutually exclusive. WebSEAL silently ignores xhtml10 if onfocus has also been specified.

If we create a junction using the xhtml10 argument, it is best practise to use the inhead argument as well. The inhead argument ensures the placement of the JavaScript within the HTML code is compliant with HTML 4.01 specifications. For example (command line fragment):

pdadmin> server task instance-webseald-host create ... -j -J inhead,xhtml10 ... 

See also Inserting the JavaScript block for HTML 4.01 compliance (inhead).

Parent topic: Control on the junction cookie JavaScript block