Netgear WFS709TP WFS709TP Setup Manual - Page 201

Appendix C Internal Captive Portal, Creating a New Internal Web

Page 201 highlights

Appendix C Internal Captive Portal You can customize the default captive portal page through the browser interface, as described in Chapter 8, "Configuring the Captive Portal".You can also create your own web page to display rather than the default page. This appendix discusses creating and installing a new internal captive portal page and other customizations. It includes the following topics: • "Creating a New Internal Web Page" on page C-1 • "Installing a New Captive Portal Page" on page C-4 • "Displaying Authentication Error Message" on page C-4 • "Language Customization" on page C-6 • "Customizing the Welcome Page" on page C-12 • "Customizing the Pop-Up Box" on page C-14 • "Customizing the Logged Out Box" on page C-15 Creating a New Internal Web Page A custom web page must include an authentication form to authenticate a user. The authentication form can include any of the following variables: • user (Required) • password (Required) • FQDN: The fully qualified domain name. Note: This is dependent on the setting of the WFS709TP ProSafe Smart Wireless Switch and is supported only by Windows global catalog server software. The form can use either the "get" or the "post" methods, but the "post" method is recommended. The form's action must absolutely or relatively reference https:///auth/index.html/u. You can construct an authentication form using the following HTML: C-1 v1.0, June 2007

  • 1
  • 2
  • 3
  • 4
  • 5
  • 6
  • 7
  • 8
  • 9
  • 10
  • 11
  • 12
  • 13
  • 14
  • 15
  • 16
  • 17
  • 18
  • 19
  • 20
  • 21
  • 22
  • 23
  • 24
  • 25
  • 26
  • 27
  • 28
  • 29
  • 30
  • 31
  • 32
  • 33
  • 34
  • 35
  • 36
  • 37
  • 38
  • 39
  • 40
  • 41
  • 42
  • 43
  • 44
  • 45
  • 46
  • 47
  • 48
  • 49
  • 50
  • 51
  • 52
  • 53
  • 54
  • 55
  • 56
  • 57
  • 58
  • 59
  • 60
  • 61
  • 62
  • 63
  • 64
  • 65
  • 66
  • 67
  • 68
  • 69
  • 70
  • 71
  • 72
  • 73
  • 74
  • 75
  • 76
  • 77
  • 78
  • 79
  • 80
  • 81
  • 82
  • 83
  • 84
  • 85
  • 86
  • 87
  • 88
  • 89
  • 90
  • 91
  • 92
  • 93
  • 94
  • 95
  • 96
  • 97
  • 98
  • 99
  • 100
  • 101
  • 102
  • 103
  • 104
  • 105
  • 106
  • 107
  • 108
  • 109
  • 110
  • 111
  • 112
  • 113
  • 114
  • 115
  • 116
  • 117
  • 118
  • 119
  • 120
  • 121
  • 122
  • 123
  • 124
  • 125
  • 126
  • 127
  • 128
  • 129
  • 130
  • 131
  • 132
  • 133
  • 134
  • 135
  • 136
  • 137
  • 138
  • 139
  • 140
  • 141
  • 142
  • 143
  • 144
  • 145
  • 146
  • 147
  • 148
  • 149
  • 150
  • 151
  • 152
  • 153
  • 154
  • 155
  • 156
  • 157
  • 158
  • 159
  • 160
  • 161
  • 162
  • 163
  • 164
  • 165
  • 166
  • 167
  • 168
  • 169
  • 170
  • 171
  • 172
  • 173
  • 174
  • 175
  • 176
  • 177
  • 178
  • 179
  • 180
  • 181
  • 182
  • 183
  • 184
  • 185
  • 186
  • 187
  • 188
  • 189
  • 190
  • 191
  • 192
  • 193
  • 194
  • 195
  • 196
  • 197
  • 198
  • 199
  • 200
  • 201
  • 202
  • 203
  • 204
  • 205
  • 206
  • 207
  • 208
  • 209
  • 210
  • 211
  • 212
  • 213
  • 214
  • 215
  • 216
  • 217
  • 218
  • 219
  • 220
  • 221
  • 222

C-1
v1.0, June 2007
Appendix C
Internal Captive Portal
You can customize the default captive portal page through the browser interface, as described in
Chapter 8, “Configuring the Captive Portal”
.You can also create your own web page to display
rather than the default page. This appendix discusses creating and installing a new internal captive
portal page and other customizations.
It includes the following topics:
“Creating a New Internal Web Page” on page C-1
“Installing a New Captive Portal Page” on page C-4
“Displaying Authentication Error Message” on page C-4
“Language Customization” on page C-6
“Customizing the Welcome Page” on page C-12
“Customizing the Pop-Up Box” on page C-14
“Customizing the Logged Out Box” on page C-15
Creating a New Internal Web Page
A custom web page must include an authentication form to authenticate a user.
The authentication form can include any of the following variables:
user
(Required)
password
(Required)
FQDN
: The fully qualified domain name.
The form can use either the “get” or the “post” methods, but the “post” method is recommended.
The form’s action must absolutely or relatively reference https://<switch_IP>/auth/index.html/u.
You can construct an authentication form using the following HTML:
Note:
This is dependent on the setting of the WFS709TP ProSafe Smart Wireless
Switch and is supported only by Windows global catalog server software.