Editing Captive portal (section)

=== HTTP redirect ===
A common method is to direct all [[World Wide Web]] traffic to a web server, which returns an [[HTTP 302|HTTP redirect]] to a captive portal.<ref>{{Cite web
| url=https://andrewwippler.com/2017/04/07/captive-portal-overview/
| title=Captive Portal Overview
| last=Wippler
| first=Andrew J.
| date=April 7, 2017
| website=Andrew Wippler's Sketchpad
| access-date=2019-03-06
| archive-date=2019-05-04
| archive-url=https://web.archive.org/web/20190504093331/https://andrewwippler.com/2017/04/07/captive-portal-overview/
| url-status=live
}}</ref> When a modern, Internet-enabled device first connects to a network, it sends out an HTTP request to a detection URL predefined by its vendor and expects an [[List_of_HTTP_status_codes#2xx success|HTTP status code]] 200 OK or 204 No Content. If the device receives a HTTP 2xx status code, it assumes it has unlimited internet access. Captive portal prompts are displayed when you are able to manipulate this first HTTP message to return a HTTP status code of 302 (redirect) to the captive portal of your choice.<ref>{{Cite web
| url=https://andrewwippler.com/2016/03/11/wifi-captive-portal/
| title=WiFi Captive Portal
| last=Wippler
| first=Andrew J.
| date=March 11, 2016
| website=Andrew Wippler's Sketchpad
| access-date=2019-03-06
| archive-date=2019-05-04
| archive-url=https://web.archive.org/web/20190504093332/https://andrewwippler.com/2016/03/11/wifi-captive-portal/
| url-status=live
}}</ref><ref>{{Cite web
| url=https://www.chromium.org/chromium-os/chromiumos-design-docs/network-portal-detection
| title=Network Portal Detection
| publisher=[[Chromium_(web_browser)|Chromium]]
| access-date=2019-03-06
| archive-date=2019-03-03
| archive-url=https://web.archive.org/web/20190303050020/http://www.chromium.org/chromium-os/chromiumos-design-docs/network-portal-detection
| url-status=live
}}</ref> {{IETF RFC|6585}} specifies the 511 Network Authentication Required status code.