rfc8908v1.xml		rfc8908.xml
	skipping to change at line 365 ¶		skipping to change at line 365 ¶
	a client connected to a captive network		a client connected to a captive network
	will query the API server to retrieve information about		will query the API server to retrieve information about
	its captive state and conditions to escape captivity. In this example,		its captive state and conditions to escape captivity. In this example,
	the client discovered the URI		the client discovered the URI
	"https://example.org/captive-portal/api/X54PD39JV" using one of the		"https://example.org/captive-portal/api/X54PD39JV" using one of the
	mechanisms defined in <xref target="RFC8910"		mechanisms defined in <xref target="RFC8910"
	format="default"/>.</t>		format="default"/>.</t>
	<t>To request the Captive Portal JSON content, a client sends an HTTP		<t>To request the Captive Portal JSON content, a client sends an HTTP
	GET request:</t>		GET request:</t>
	<sourcecode type=""><![CDATA[		<sourcecode type="http-message"><![CDATA[
	GET /captive-portal/api/X54PD39JV HTTP/1.1		GET /captive-portal/api/X54PD39JV HTTP/1.1
	Host: example.org		Host: example.org
	Accept: application/captive+json		Accept: application/captive+json
	]]></sourcecode>		]]></sourcecode>
	<t>The server then responds with the JSON content for that client:</t>		<t>The server then responds with the JSON content for that client:</t>
	<sourcecode type=""><![CDATA[		<sourcecode type="http-message"><![CDATA[
	HTTP/1.1 200 OK		HTTP/1.1 200 OK
	Cache-Control: private		Cache-Control: private
	Date: Mon, 02 Mar 2020 05:07:35 GMT		Date: Mon, 02 Mar 2020 05:07:35 GMT
	Content-Type: application/captive+json		Content-Type: application/captive+json
	{		{
	"captive": true,		"captive": true,
	"user-portal-url": "https://example.org/portal.html"		"user-portal-url": "https://example.org/portal.html"
	}		}
	]]></sourcecode>		]]></sourcecode>
	<t>Upon receiving this information, the client will use it		<t>Upon receiving this information, the client will use it
	to direct the user to the web portal (as specified by the		to direct the user to the web portal (as specified by the
	user-portal-url value) to enable access to the external network. Once		user-portal-url value) to enable access to the external network. Once
	the user satisfies the requirements for external network access, the		the user satisfies the requirements for external network access, the
	client <bcp14>SHOULD</bcp14> query the API server again to verify that		client <bcp14>SHOULD</bcp14> query the API server again to verify that
	it is no longer captive.</t>		it is no longer captive.</t>
	<t>When the client requests the Captive Portal JSON content after		<t>When the client requests the Captive Portal JSON content after
	gaining external network access, the server responds with updated JSON		gaining external network access, the server responds with updated JSON
	content:</t>		content:</t>
	<sourcecode type=""><![CDATA[		<sourcecode type="http-message"><![CDATA[
	HTTP/1.1 200 OK		HTTP/1.1 200 OK
	Cache-Control: private		Cache-Control: private
	Date: Mon, 02 Mar 2020 05:08:13 GMT		Date: Mon, 02 Mar 2020 05:08:13 GMT
	Content-Type: application/captive+json		Content-Type: application/captive+json
	{		{
	"captive": false,		"captive": false,
	"user-portal-url": "https://example.org/portal.html",		"user-portal-url": "https://example.org/portal.html",
	"venue-info-url": "https://flight.example.com/entertainment",		"venue-info-url": "https://flight.example.com/entertainment",
	"seconds-remaining": 326,		"seconds-remaining": 326,
End of changes. 3 change blocks.
	3 lines changed or deleted		3 lines changed or added
This html diff was produced by rfcdiff 1.48. The latest version is available from http://tools.ietf.org/tools/rfcdiff/