Allied Telesis AT-WR4500 manual Customizing HotSpot Http Servlet Pages, Serving Servlet Pages

236	AT-WR4500 Series - IEEE 802.11abgh Outdoor Wireless Routers
	RouterOS v3 Configuration and User Guide

10.3.10 Customizing HotSpot: HTTP Servlet Pages

Description

You can create a completely different set of servlet pages for each HotSpot server you have, specifying the directory it will be stored in html-directoryproperty of a HotSpot server profile (/ip hotspot profile). The default servlet pages are copied in the directory of your choice right after you create the profile. This directory can be accessed by connecting to the router with an FTP client. You can modify the pages as you like using the information from this section of the manual.

Available Servlet Pages

Main HTML servlet pages, which are shown to user:

redirect.html - redirects user to another url (for example, to login page)

login.html - login page shown to a user to ask for username and password. This page may take the following parameters:

username - username

password - either plain-text password (in case of PAP authentication) or MD5 hash of chap-idvariable, password and CHAP challenge (in case of CHAP authentication). This value is used as e-mail address for trial users

dst - original URL requested before the redirect. This will be opened on successfull login popup - whether to pop-up a status window on successfull login

radius<id> - send the attribute identified with <id> in text string form to the RADIUS server (in case RADIUS authentication is used; lost otherwise)

radius<id>u - send the attribute identified with <id> in unsigned integer form to the RADIUS server (in case RADIUS authentication is used; lost otherwise)

radius<id>-<vnd-id>- send the attribute identified with <id> and vendor ID <vnd-id> in text string form to the RADIUS server (in case RADIUS authentication is used; lost otherwise) radius<id>-<vnd-id>u- send the attribute identified with <id> and vendor ID <vnd-id> in unsigned integer form to the RADIUS server (in case RADIUS authentication is used; lost otherwise)

md5.js - JavaScript for MD5 password hashing. Used together with http-chaplogin method alogin.html - page shown after client has logged in. It pops-up status page and redirects browser to originally requested page (before he/she was redirected to the HotSpot login page)

status.html - status page, shows statistics for the client. It is also able to display advertisements automatically

logout.html - logout page, shown after user is logged out. Shows final statistics about the finished session. This page may take the following additional parameters:

erase-cookie- whether to erase cookies from the HotSpot server on logout (makes impossible to log in with cookie next time from the same browser, might be useful in multiuser environments) error.html - error page, shown on fatal errors only

Some other pages are available as well, if more control is needed:

rlogin.html - page, which redirects client from some other URL to the login page, if authorization of the client is required to access that URL

rstatus.html - similarly to rlogin.html, only in case if the client is already logged in and the original URL is not known

radvert.html - redirects client to the scheduled advertisement link

flogin.html - shown instead of login.html, if some error has happened (invalid username or password, for example)

fstatus.html - shown instead of redirect, if status page is requested, but client is not logged in flogout.html - shown instead of redirect, if logout page is requested, but client is not logged in

Serving Servlet Pages

The HotSpot servlet recognizes 5 different request types: request for a remote host

if user is logged in and advertisement is due to be displayed, radvert.html is displayed. This page makes redirect to the scheduled advertisment page

if user is logged in and advertisement is not scheduled for this user, the requested page is served if user is not logged in, but the destination host is allowed by walled garden, then the request is also served

if user is not logged in, and the destination host is disallowed by walled garden, rlogin.html is displayed; if rlogin.html is not found, redirect.html is used to redirect to the login page

request for "/" on the HotSpot host