You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I have a use case, where I'm trying to use Apache reverse proxy to act as a HTTPS reverse proxy that redirect https://HOST/git-lfs/ to a backend lfs-test-server that's serving HTTP on locahost-only port 9999 (with non-root user that doesn't have access to SSL certificates).
The problem is, if I set LFS_HOST to https://HOST/git-lfs/, lfs-test-server builds malformed URLs like http://https://HOST/git-lfs/.
I propose checking if LFS_HOST starts with a protocol definition, and if so, omitting the http:// prefix it normally adds.
The text was updated successfully, but these errors were encountered:
elonen
changed the title
LFS_HOST insufficient when using HTTPS -> backend HTTP reverse proxy
LFS_HOST insufficient when using HTTPS -> HTTP reverse proxy
Sep 28, 2017
I have a use case, where I'm trying to use Apache reverse proxy to act as a HTTPS reverse proxy that redirect
https://HOST/git-lfs/
to a backend lfs-test-server that's serving HTTP on locahost-only port 9999 (with non-root user that doesn't have access to SSL certificates).The problem is, if I set LFS_HOST to
https://HOST/git-lfs/
, lfs-test-server builds malformed URLs likehttp://https://HOST/git-lfs/
.I propose checking if LFS_HOST starts with a protocol definition, and if so, omitting the
http://
prefix it normally adds.The text was updated successfully, but these errors were encountered: