ML
    • Recent
    • Categories
    • Tags
    • Popular
    • Users
    • Groups
    • Register
    • Login

    wget vs. curl

    Scheduled Pinned Locked Moved IT Discussion
    wgetcurldiscussion
    9 Posts 5 Posters 2.5k Views
    Loading More Posts
    • Oldest to Newest
    • Newest to Oldest
    • Most Votes
    Reply
    • Reply as topic
    Log in to reply
    This topic has been deleted. Only users with topic management privileges can see it.
    • wirestyle22W
      wirestyle22
      last edited by wirestyle22

      curl supports FTP, FTPS, HTTP, HTTPS, SCP, SFTP, TFTP, TELNET, DICT, LDAP, LDAPS, FILE, POP3, IMAP, SMTP, RTMP and RTSP.

      wget supports HTTP, HTTPS and FTP.

      wget is part of the GNU project and all copyrights are assigned to FSF.

      curl project is entirely stand-alone and independent with no organization parenting at all

      curl offers upload and sending capabilities. .

      Seems to me we should be using curl 99% of the time and wget when we have to deal with a lot of things simultaneously? Am I judging that correctly? Otherwise there does not seem to be a benefit.

      travisdh1T 1 Reply Last reply Reply Quote 0
      • travisdh1T
        travisdh1 @wirestyle22
        last edited by

        @wirestyle22 said in wget vs. curl:

        curl supports FTP, FTPS, HTTP, HTTPS, SCP, SFTP, TFTP, TELNET, DICT, LDAP, LDAPS, FILE, POP3, IMAP, SMTP, RTMP and RTSP.

        wget supports HTTP, HTTPS and FTP.

        wget is part of the GNU project and all copyrights are assigned to FSF.

        curl project is entirely stand-alone and independent with no organization parenting at all
        curl offers upload and sending capabilities. .

        Seems to me we should be using curl 99% of the time and wget when we have to deal with a lot of things simultaneously? Am I judging that correctly? Otherwise there does not seem to be a benefit.

        I tend to use wget, just because it's what I'm used to. I know curl can do more, but being able to do more isn't always the simple/quick way to go about things, unless you're doing one of @scottalanmiller's one-liners.

        wirestyle22W 1 Reply Last reply Reply Quote 2
        • wirestyle22W
          wirestyle22 @travisdh1
          last edited by wirestyle22

          @travisdh1 said in wget vs. curl:

          @wirestyle22 said in wget vs. curl:

          curl supports FTP, FTPS, HTTP, HTTPS, SCP, SFTP, TFTP, TELNET, DICT, LDAP, LDAPS, FILE, POP3, IMAP, SMTP, RTMP and RTSP.

          wget supports HTTP, HTTPS and FTP.

          wget is part of the GNU project and all copyrights are assigned to FSF.

          curl project is entirely stand-alone and independent with no organization parenting at all
          curl offers upload and sending capabilities. .

          Seems to me we should be using curl 99% of the time and wget when we have to deal with a lot of things simultaneously? Am I judging that correctly? Otherwise there does not seem to be a benefit.

          I tend to use wget, just because it's what I'm used to. I know curl can do more, but being able to do more isn't always the simple/quick way to go about things, unless you're doing one of @scottalanmiller's one-liners.

          Just a thought I had when I was testing some stuff on my vultr instance. You'll likely have both.

          JaredBuschJ 1 Reply Last reply Reply Quote 0
          • JaredBuschJ
            JaredBusch @wirestyle22
            last edited by

            @wirestyle22 said in wget vs. curl:

            @travisdh1 said in wget vs. curl:

            @wirestyle22 said in wget vs. curl:

            curl supports FTP, FTPS, HTTP, HTTPS, SCP, SFTP, TFTP, TELNET, DICT, LDAP, LDAPS, FILE, POP3, IMAP, SMTP, RTMP and RTSP.

            wget supports HTTP, HTTPS and FTP.

            wget is part of the GNU project and all copyrights are assigned to FSF.

            curl project is entirely stand-alone and independent with no organization parenting at all
            curl offers upload and sending capabilities. .

            Seems to me we should be using curl 99% of the time and wget when we have to deal with a lot of things simultaneously? Am I judging that correctly? Otherwise there does not seem to be a benefit.

            I tend to use wget, just because it's what I'm used to. I know curl can do more, but being able to do more isn't always the simple/quick way to go about things, unless you're doing one of @scottalanmiller's one-liners.

            Just a thought I had when I was testing some stuff on my vultr instance. You'll likely have both.

            Curl is native to RHEL/Fedora based systems. While wget has to be added.

            wirestyle22W travisdh1T 2 Replies Last reply Reply Quote 2
            • wirestyle22W
              wirestyle22 @JaredBusch
              last edited by

              @jaredbusch said in wget vs. curl:

              @wirestyle22 said in wget vs. curl:

              @travisdh1 said in wget vs. curl:

              @wirestyle22 said in wget vs. curl:

              curl supports FTP, FTPS, HTTP, HTTPS, SCP, SFTP, TFTP, TELNET, DICT, LDAP, LDAPS, FILE, POP3, IMAP, SMTP, RTMP and RTSP.

              wget supports HTTP, HTTPS and FTP.

              wget is part of the GNU project and all copyrights are assigned to FSF.

              curl project is entirely stand-alone and independent with no organization parenting at all
              curl offers upload and sending capabilities. .

              Seems to me we should be using curl 99% of the time and wget when we have to deal with a lot of things simultaneously? Am I judging that correctly? Otherwise there does not seem to be a benefit.

              I tend to use wget, just because it's what I'm used to. I know curl can do more, but being able to do more isn't always the simple/quick way to go about things, unless you're doing one of @scottalanmiller's one-liners.

              Just a thought I had when I was testing some stuff on my vultr instance. You'll likely have both.

              Curl is native to RHEL/Fedora based systems. While wget has to be added.

              Yeah but I never see anyone complaining about resources used or anything as it's so minor. You're right though

              1 Reply Last reply Reply Quote 0
              • travisdh1T
                travisdh1 @JaredBusch
                last edited by

                @jaredbusch said in wget vs. curl:

                @wirestyle22 said in wget vs. curl:

                @travisdh1 said in wget vs. curl:

                @wirestyle22 said in wget vs. curl:

                curl supports FTP, FTPS, HTTP, HTTPS, SCP, SFTP, TFTP, TELNET, DICT, LDAP, LDAPS, FILE, POP3, IMAP, SMTP, RTMP and RTSP.

                wget supports HTTP, HTTPS and FTP.

                wget is part of the GNU project and all copyrights are assigned to FSF.

                curl project is entirely stand-alone and independent with no organization parenting at all
                curl offers upload and sending capabilities. .

                Seems to me we should be using curl 99% of the time and wget when we have to deal with a lot of things simultaneously? Am I judging that correctly? Otherwise there does not seem to be a benefit.

                I tend to use wget, just because it's what I'm used to. I know curl can do more, but being able to do more isn't always the simple/quick way to go about things, unless you're doing one of @scottalanmiller's one-liners.

                Just a thought I had when I was testing some stuff on my vultr instance. You'll likely have both.

                Curl is native to RHEL/Fedora based systems. While wget has to be added.

                Yep, and it's so automatic to install nano and wget for me that it's almost an afterthought, in addition to any VM templates I have available.

                wirestyle22W 1 Reply Last reply Reply Quote 2
                • wirestyle22W
                  wirestyle22 @travisdh1
                  last edited by

                  @travisdh1 said in wget vs. curl:

                  @jaredbusch said in wget vs. curl:

                  @wirestyle22 said in wget vs. curl:

                  @travisdh1 said in wget vs. curl:

                  @wirestyle22 said in wget vs. curl:

                  curl supports FTP, FTPS, HTTP, HTTPS, SCP, SFTP, TFTP, TELNET, DICT, LDAP, LDAPS, FILE, POP3, IMAP, SMTP, RTMP and RTSP.

                  wget supports HTTP, HTTPS and FTP.

                  wget is part of the GNU project and all copyrights are assigned to FSF.

                  curl project is entirely stand-alone and independent with no organization parenting at all
                  curl offers upload and sending capabilities. .

                  Seems to me we should be using curl 99% of the time and wget when we have to deal with a lot of things simultaneously? Am I judging that correctly? Otherwise there does not seem to be a benefit.

                  I tend to use wget, just because it's what I'm used to. I know curl can do more, but being able to do more isn't always the simple/quick way to go about things, unless you're doing one of @scottalanmiller's one-liners.

                  Just a thought I had when I was testing some stuff on my vultr instance. You'll likely have both.

                  Curl is native to RHEL/Fedora based systems. While wget has to be added.

                  Yep, and it's so automatic to install nano and wget for me that it's almost an afterthought, in addition to any VM templates I have available.

                  Same. I'd imagine it's the same type of argument as nano vs. vi

                  RamblingBipedR 1 Reply Last reply Reply Quote 1
                  • RamblingBipedR
                    RamblingBiped @wirestyle22
                    last edited by

                    @wirestyle22 said in wget vs. curl:

                    @travisdh1 said in wget vs. curl:

                    @jaredbusch said in wget vs. curl:

                    @wirestyle22 said in wget vs. curl:

                    @travisdh1 said in wget vs. curl:

                    @wirestyle22 said in wget vs. curl:

                    curl supports FTP, FTPS, HTTP, HTTPS, SCP, SFTP, TFTP, TELNET, DICT, LDAP, LDAPS, FILE, POP3, IMAP, SMTP, RTMP and RTSP.

                    wget supports HTTP, HTTPS and FTP.

                    wget is part of the GNU project and all copyrights are assigned to FSF.

                    curl project is entirely stand-alone and independent with no organization parenting at all
                    curl offers upload and sending capabilities. .

                    Seems to me we should be using curl 99% of the time and wget when we have to deal with a lot of things simultaneously? Am I judging that correctly? Otherwise there does not seem to be a benefit.

                    I tend to use wget, just because it's what I'm used to. I know curl can do more, but being able to do more isn't always the simple/quick way to go about things, unless you're doing one of @scottalanmiller's one-liners.

                    Just a thought I had when I was testing some stuff on my vultr instance. You'll likely have both.

                    Curl is native to RHEL/Fedora based systems. While wget has to be added.

                    Yep, and it's so automatic to install nano and wget for me that it's almost an afterthought, in addition to any VM templates I have available.

                    Same. I'd imagine it's the same type of argument as nano vs. vi

                    If you're not using vi/vim, you're just wrong. No real argument.

                    Realistically, regardless of preference for wget, you should understand how to use curl. (same with vi)

                    1 Reply Last reply Reply Quote 3
                    • scottalanmillerS
                      scottalanmiller
                      last edited by

                      Yup, I prefer wget but have mostly stopped using it (or installing it.) I learned wget before I knew of curl (this is all long ago.) Today, I just assume that I have curl and wget is nearly never there.

                      1 Reply Last reply Reply Quote 3
                      • 1 / 1
                      • First post
                        Last post