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

395
Rules on page requests
The local portal server supports only Post and Get requests.
• Get requests are 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 are used when users submit usernames and passwords, log on to the system, and log
off the system.
Rules on Post request attributes
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, and the password attribute is fixed as PtPwd.
• Attribute PtButton is required to indicate the action that the user requests, which can be 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.
<form action=logon.cgi method = post >
<p>User name:<input type="text" name = "PtUser" style="width:160px;height:22px"
maxlength=64>
<p>Password :<input type="password" name = "PtPwd" style="width:160px;height:22px"
maxlength=32>
<p><input type=SUBMIT value="Logon" name = "PtButton" style="width:60px;"
onclick="form.action=form.action+location.search;>
</form>
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.
<form action=logon.cgi method = post >
<p><input type=SUBMIT value="Logoff" name="PtButton" style="width:60px;">
</form>
Rules on page file compression and saving
• A set of authentication page files must be compressed into a standard zip file. The name of a zip
file can contain only letters, digits, and underscores. The zip file of the default authentication pages
must be saved with the name defaultfile.zip.
• The set of authentication pages must be located in the root directory of the zip file.
• Zip files can be transferred to the device through FTP or TFTP. The default authentication pages file
must be saved in the root directory of the device, and customized authentication files can be saved
in the root directory or in the portal directory under the root directory of the device.
Rules on file size and contents
For the system to push customized authentication pages smoothly, you need comply with the following
size and content requirements on authentication pages.