From d4faf9f1907f18efbd06008e73723fbb3f16b6d2 Mon Sep 17 00:00:00 2001 From: Tony Heap Date: Mon, 26 Nov 2018 21:29:53 +0000 Subject: [PATCH] APIS-3862 - further changes to reference guide page that I missed first time round --- app/uk/gov/hmrc/apidocumentation/views/reference.scala.html | 5 +++-- 1 file changed, 3 insertions(+), 2 deletions(-) diff --git a/app/uk/gov/hmrc/apidocumentation/views/reference.scala.html b/app/uk/gov/hmrc/apidocumentation/views/reference.scala.html index bd70762d..9bbe3456 100644 --- a/app/uk/gov/hmrc/apidocumentation/views/reference.scala.html +++ b/app/uk/gov/hmrc/apidocumentation/views/reference.scala.html @@ -680,10 +680,10 @@

Header Contents

then add :
"for=<Gov-Client-Local-IP>;by=<current IP>"

If no value is defined, and the request came from some other IP address (not the - Gov-Client-Local-IP), then add :
+ Gov-Client-Local-IP), then add:
"for=<Gov-Client-Local-IP>, for=<IP request came from>;by=<current IP>"

- If the value is defined, then append the following to the existing value :
+ If the value is defined, then append the following to the existing value:
", for=<IP request came from>;by=<current IP>"

For more details on this header field, see IETF RFC7239 (opens in a new tab). @@ -738,6 +738,7 @@

Redirect URIs

You must specify one or more redirect URIs when you create your application, and also specify one redirect URI when you send your user to our authorisation endpoint. To protect your application from phishing attacks, the redirect URI used for authorisation must match one of those specified when you created your application.

+

You can specify a maximum of five redirect URIs.

Examples

Examples of valid (and invalid) redirect URIs are: