Open AntonZhuchkovXOR opened 9 months ago
Late response to a question still relevant. Couple of options at present:
allowInsecureConnections
to true
as described here to suppress the warningYou could put LiGet behind a reverse proxy such as Apache or nginx. e.g. Apache config:
<VirtualHost *:443>
ServerName nuget.company.com
ServerAlias nuget.company.com *.nuget.company.com
ErrorLog ${APACHE_LOG_DIR}/httpsnuget_error.log
CustomLog ${APACHE_LOG_DIR}/httpsnuget_access.log combined
ProxyRequests Off
<Proxy *>
Order deny,allow
Allow from all
</Proxy>
ProxyPreserveHost On
RequestHeader set X-Forwarded-Proto "https"
ProxyPass / http://internal-url.com:9011/
ProxyPassReverse / http://internal-url:9011/
SSLEngine on
SSLProtocol all -SSLv2 -SSLv3
SSLCertificateFile /etc/tlscerts/nuget.pem
SSLCertificateChainFile /etc/tlscerts/nuget.pem
I am currently utilizing Liget for local development within Docker, and I consistently encounter a warning from MSBuild:
I'm curious if there are any plans to implement HTTPS support for Liget. The tool has proven to be extremely valuable for my workflow, and I would like to continue using it.