The Portable Freeware Collection Forums

INetGet is a simple command-line interface to the WinINet API. In other words, it is a program for downloading files via the HTTP (Hypertext Transfer Protocol) or FTP (File Transfer Protocol) protocols. It provides full support for HTTPS (HTTP over TLS) as well as IPv6.



This program provides a similar functionality as the well-known WGet and cURL tools. However, in contrast to those, INetGet is based directly on the "native" Windows Internet programming interface (WinINet). This comes at the advantage that INetGet is very small and lightweight, as it uses the HTTP(S) and FTP services provided by the operating system, instead of having to implement these protocols on its own. There are no external dependencies (e.g. OpenSSL or GnuTLS), except for standard system libraries that are present on every Windows system anyway. Still, advanced features, such as HTTPS and IPv6, are supported. Furthermore, since INetGet is based on the Windows crypto libraries, it uses the Windows certificate store. This means that, in contrast the aforementioned tools, you do not need to provide and maintain your own certificate bundle for HTTPS. Certificate updates as well as security fixes for the underlying cryptographic routines are automatically provided, via Windows Update. On the downside, you will have to trust Microsoft's protocol implementations.

Download:
https://github.com/lordmulder/INetGet/releases/latest

User Manual:
http://muldersoft.com/docs/inetget_readme.html

Excellent work, thanks.

A suggestion: as Wget does, INetGet should be able to read 'inetget.ini' (if present) for persistent directives (i.e., options), e.g., user agent string; this file would be parsed first and over-ridden if different options are explicitly declared via the command line while invoking the program...

This is cool but I'll wait until it has some features that curl/wget have like time-stamping to detect newer data. I use these downloaders to update apps/webpage archives. I don't wanna be wasting bandwidth downloading and overwriting the same old data again.

INetGet v1.01:
https://github.com/lordmulder/INetGet/releases/tag/1.01

Moving out of Submission as this can't get added to the database ... http://www.portablefreeware.com/faq.php#six

Why read-only attributes?

Userfriendly wrote:This is cool but I'll wait until it has some features that curl/wget have like time-stamping to detect newer data. I use these downloaders to update apps/webpage archives. I don't wanna be wasting bandwidth downloading and overwriting the same old data again.

This is more a "high level" function that probably won't be implemented in INetGet directly. It requires multiple HTTP requests (one HEAD request to fetch header and check the last modification date, plus one GET request to actually fetch the data). And it can only work if the server actually sent a "Last-Modified" header field - which isn't always the case. So this is more something that could be scripted, using INetGet to perform the required HTTP requests. What could be added easily (more or less) is an INetGet option that will set the "LastWriteTime" of the output file to the date that the server sent in its "Last-Modified" header field - if such a field is present in the server's reply.

billon wrote:Why read-only attributes?

To protect the release binaries from (inadvertent) modifications. Why would you ever want to (intentionally) modify the release binaries? If you wanted to modify the program in whatever way, you'd just grab the original source codes, from the official GIT repo, apply your desired modifications and compile a new binary. You certainly would not want to "hack" on the existing release binary. Anyway, removing the "ready only" attribute requires only one or two clicks - should it ever be required.

Userfriendly wrote:This is cool but I'll wait until it has some features that curl/wget have like time-stamping to detect newer data. I use these downloaders to update apps/webpage archives. I don't wanna be wasting bandwidth downloading and overwriting the same old data again.

Okay, you can try with this Test version:
http://sourceforge.net/projects/mulders ... p/download

Please see the included REAMDE file for the "--set-ftime" and "--update" options, which should be doing what you want...

Just tested it and it works fine so far. I think I got a new favorite downloader Already replaced wget and curl with this since those require much more complicated command options.

You'll probably make a GUI frontend for this at some point like most of your other projects?

Here is a new TEST version:
http://sourceforge.net/projects/mulders ... p/download

Biggest difference is that I moved all the I/O stuff into separate worker threads now, in order to make the application more responsive. You will notice this, e.g., if you unplug the network cable in the middle of a transfer. Before, the application would just "freeze" completely in this case - until the network timeout triggers. Now, you will see that the application remains "responsive" and the transfer rate continuously goes down (because no more data is received). Also, Ctrl+C events will now be handled much faster.

INetGet v1.02 (2018-03-31):
https://github.com/lordmulder/INetGet/releases/tag/1.02

Who is "kendo master"?

Midas wrote: ↑Sun Apr 01, 2018 2:24 am Who is "kendo master"?

There can be only one... https://youtu.be/g6nLRHUg_r8