From b394f05feea1f78359c7a734a1f548faf0cf88ec Mon Sep 17 00:00:00 2001 From: Yi EungJun Date: Wed, 6 Apr 2016 16:10:30 +0900 Subject: [PATCH] Use 'null' instead of 'nil' for json When describe json response, 'null' is better than 'nil' which is not in json specification. Signed-off-by: Yi EungJun --- docs/extend/plugins_authorization.md | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/docs/extend/plugins_authorization.md b/docs/extend/plugins_authorization.md index 6ebed3542f..a47cd2a55b 100644 --- a/docs/extend/plugins_authorization.md +++ b/docs/extend/plugins_authorization.md @@ -196,8 +196,8 @@ should implement the following two methods: "Allow": "Determined whether the user is allowed or not", "Msg": "The authorization message", "Err": "The error message if things go wrong", - "ModifiedBody": "Byte array containing a modified body of the raw HTTP body (or nil if no changes required)", - "ModifiedHeader": "Byte array containing a modified header of the HTTP response (or nil if no changes required)", + "ModifiedBody": "Byte array containing a modified body of the raw HTTP body (or null if no changes required)", + "ModifiedHeader": "Byte array containing a modified header of the HTTP response (or null if no changes required)", "ModifiedStatusCode": "int containing the modified version of the status code (or 0 if not change is required)" } ```