Open lalten opened 5 months ago
What would you like to achieve? Can you describe your use case for this? Looking at the link, I see that .netrc is somehow related to automatic login (to FTP?) on GNU systems. It is not clear to me how this would relate to zsync2.
.netrc is a standard way to provide credentials and not only used for FTP. wget uses it automatically, and curl uses it when you supply -n/--netrc
.
My https://example.com/artifact.appimage will return 404 without the right credentials passed in the authorization header.
Thanks for the clarification. I don't think this is a planned feature but if we'd get a pull request we'd definitely consider it. My only worry is that it might introduce additional complexity and/or security attack vectors, and hence increase maintenance burden.
zsync2 does not offer .netrc support.
As a workaround, you can pass credentials directly in the URL like
Any plans to support this?