-
Notifications
You must be signed in to change notification settings - Fork 11
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Question : ByPass Authorization for visualizing clip behind reverse proxy ? #126
Comments
@Nonobis you should set But please note, this notation doesn't work with Telegram, it will disable this link |
@freefd : I can encode password in base64 ? or it's must be in plain text ... it's not really secure |
@Nonobis, well, a little longer explanation then :) As per the RFC3986, this old known form has been marked as deprecated, but is still supported by any browser or http lib, and would work anyway. I believe, your reverse proxy is authenticating requests already, so the possible solutions could be:
|
not working ... i will wait and hope for #98 to be implemented one as an alternative. |
just as a note, base64 is encoding, not encryption and is not really safer than plaintext. And the username:password@ gets translated into a basic auth header with the encoded username/password and if using SSL, they should be encrypted at that point. I certainly understand being hesitant to be use urls with username/password as can end up in your browsing history... or possibly cached somewhere. I do it, but I understand why others do not. |
Hi there, can it be closed in favor of #98? |
Yes, including clip better i think |
I am behind Ngninx Proxy Manager, how do you bypass auth when clicking on video/.snapshot link on received notification ?
The text was updated successfully, but these errors were encountered: