ThatGuyJack/nginx-proxy-manager
1
0
Fork 0
mirror of https://github.com/NginxProxyManager/nginx-proxy-manager.git synced 2025-08-08 10:23:37 +00:00
Code Issues Actions 1 Packages Projects Releases Wiki Activity

Remove incorrect apostrophe

Browse Source 
"...using NodeJS and it's long list of..."

This means "NodeJS and it is long list of..." The possessive form you wanted is "its"
This commit is contained in:
Term14
2022-01-30 11:26:30 -06:00
committed by GitHub
parent a233bc0045
commit 2dc97f511d
1 changed files with 2 additions and 2 deletions
Download Patch File Download Diff File Expand all files Collapse all files

4
docs/faq/README.md
View File

@@ -5,7 +5,7 @@
Yes, that's how this project is packaged. 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 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. 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. ## 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. 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.