H3C Technologies H3C WX3000E Series Wireless Switches - Manual (Page 557)

536
Main authentication page File name
Online page.
Pushed after the user gets online for online notification.
online.htm
System busy page.
Pushed when the system is busy or the user is in the logon process.
busy.htm
Logoff success page. logoffSuccess.htm
Page request rules
The local portal server supports only Post and Get requests.
• Get requests—Used to get the static files in the authentication pages, and allow no recursion. For
example, if file logon.htm includes contents that perform Get action on file ca.htm, file ca.htm
cannot include any reference to file logon.htm.
• Post requests—Used when users submit usernames and passwords, log on to the system, and log off
the system.
Post request attribute rules
1. Observe the following requirements when editing a form of an authentication page:
An authentication page can have multiple forms, but there must be one and only one form
whose action is logon.cgi. Otherwise, user information cannot be sent to the local portal server.
The username attribute is fixed as PtUser. The password attribute is fixed as PtPwd.
Attribute PtButton is required to indicate the action that the user requests, either Logon or Logoff.
A logon Post request must contain PtUser, PtPwd, and PtButton attributes.
A logoff Post request must contain the PtButton attribute.
2. Authentication pages logon.htm and logonFail.htm must contain the logon Post request.
The following example shows part of the script in page logon.htm.
User name:
maxlength=64>
Password :
maxlength=32>
onclick="form.action=form.action+location.search;>
3. Authentication pages logonSuccess.htm and online.htm must contain the logoff Post request.
The following example shows part of the script in page online.htm.