When a URL is clicked or a form is submitted, the browser sends the action to an HTTP server, which in turn calls the WebAccess servlet. If action is specified, the servlet calls the provider and then uses a template to generate the resulting HTML page. If no template is specified, login.htt is used.
For more information about how to handle errors, see
To specify a template, include the word “merge” accompanied by the name of the template to be used.
Templates always end with an .htt extension, but the extension is not included when specifying the name of the template. For example,
. . .&merge=webacc
uses the webacc.htt template file to generate the HTML that is sent back to the browser.
For more information on templates, see the Template Documentation and the following two examples:
<A href="/servlet/webacc?Provider.name=GWAP&action= User.Login&User.id=jdoe&User.password=skiutah&merge=webacc">Login</A>
<FORM method=post action=/servlet/webacc>
<INPUT type=hidden name="Provider.name" value="GWAP">
<INPUT type=hidden name="merge" value="webacc">
<INPUT type=hidden name="action" value="User.Login">
User Id:
<INPUT type=input name="User.id" value=""><BR>
Password:
<INPUT type=password name="User.password" value=""><BR>
</FORM>
Since GWAP is the default provider for the WebAccess servlet, Provider.name is not necessary in the previous example.
To specify that a different template be used if an error occurs during processing, include the word “error” accompanied by the name of the template to be used. For example
. . .&merge=webacc&error=errfile. . .