From 2dc97f511d3eb0ab6980cf0492fcae2727a32425 Mon Sep 17 00:00:00 2001 From: Term14 <64224516+Term14@users.noreply.github.com> Date: Sun, 30 Jan 2022 11:26:30 -0600 Subject: [PATCH] Remove incorrect apostrophe "...using NodeJS and it's long list of..." This means "NodeJS and it is long list of..." The possessive form you wanted is "its" --- docs/faq/README.md | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/docs/faq/README.md b/docs/faq/README.md index cf739ead..2648a5d4 100644 --- a/docs/faq/README.md +++ b/docs/faq/README.md @@ -5,7 +5,7 @@ Yes, that's how this project is packaged. This makes it easier to support the project when I have control over the version of Nginx and NodeJS -being used. In future this could change if the backend was no longer using NodeJS and it's long list +being used. In future this could change if the backend was no longer using NodeJS and its long list of dependencies. @@ -23,4 +23,4 @@ Gitter is best left for anyone contributing to the project to ask for help about ## When adding username and password access control to a proxy host, I can no longer login into the app. -Having an Access Control List (ACL) with username and password requires the browser to always send this username and password in the `Authorization` header on each request. If your proxied app also requires authentication (like Nginx Proxy Manager itself), most likely the app will also use the `Authorization` header to transmit this information, as this is the standardized header meant for this kind of information. However having multiples of the same headers is not allowed in the [internet standard](https://www.rfc-editor.org/rfc/rfc7230#section-3.2.2) and almost all apps do not support multiple values in the `Authorization` header. Hence one of the two logins will be broken. This can only be fixed by either removing one of the logins or by changing the app to use other non-standard headers for authorization. \ No newline at end of file +Having an Access Control List (ACL) with username and password requires the browser to always send this username and password in the `Authorization` header on each request. If your proxied app also requires authentication (like Nginx Proxy Manager itself), most likely the app will also use the `Authorization` header to transmit this information, as this is the standardized header meant for this kind of information. However having multiples of the same headers is not allowed in the [internet standard](https://www.rfc-editor.org/rfc/rfc7230#section-3.2.2) and almost all apps do not support multiple values in the `Authorization` header. Hence one of the two logins will be broken. This can only be fixed by either removing one of the logins or by changing the app to use other non-standard headers for authorization.