Local HTTP Redirect Server Operation Flow
You can use the local HTTP redirect feature in configurations where the redirect server resides locally on the router.
An HTTP redirect local server that resides locally on a router processes HTTP requests redirected to it and responds with a redirect URL to a captive portal. You can implement the local server as a service within a service set, which provides more scalability and better performance. When you use a local HTTP redirect server, you need to configure an HTTP service rule to redirect HTTP requests to a captive portal within a walled garden.
The following general sequence occurs during access configuration for a local HTTP redirect server deployment:
- The subscriber logs in.
- RADIUS authenticates the subscriber and sends a service activate (HTTP redirect), which redirects HTTP traffic to the captive portal in a walled garden.
- The subscriber attempts to access the content server (HTTP traffic).
- The subscriber’s HTTP traffic is redirected to the captive portal by the router.
- The captive portal sends an authorization page back to the subscriber.
- The subscriber enters credentials to obtain authorization.
- The captive portal verifies the subscriber credentials.
- The captive portal authorizes the subscriber.
The subscriber now has access to the content server.
The following example shows a configuration for HTTP redirect:
[edit services captive-portal-content-delivery]
rule redirect {
match-direction input-output
term 1 {
from {
applications junos-http;
}
then {
redirect http://100.20.2.10/index.html; # this is the captive portal page }
}
}