`curl -O` stores an empty file though `wget` works well

The name of the pictureThe name of the pictureThe name of the pictureClash Royale CLAN TAG#URR8PPP








up vote
1
down vote

favorite












I have tried to download a file from https://logz.io/sample-data.



curl -O https://logz.io/sample-data


However, it just returns an empty file named sample-data.



In contrast to curl, however, wget works well returning a file containing proper contents.



wget https://logz.io/sample-data 


What have I missed with curl?







share|improve this question


























    up vote
    1
    down vote

    favorite












    I have tried to download a file from https://logz.io/sample-data.



    curl -O https://logz.io/sample-data


    However, it just returns an empty file named sample-data.



    In contrast to curl, however, wget works well returning a file containing proper contents.



    wget https://logz.io/sample-data 


    What have I missed with curl?







    share|improve this question
























      up vote
      1
      down vote

      favorite









      up vote
      1
      down vote

      favorite











      I have tried to download a file from https://logz.io/sample-data.



      curl -O https://logz.io/sample-data


      However, it just returns an empty file named sample-data.



      In contrast to curl, however, wget works well returning a file containing proper contents.



      wget https://logz.io/sample-data 


      What have I missed with curl?







      share|improve this question














      I have tried to download a file from https://logz.io/sample-data.



      curl -O https://logz.io/sample-data


      However, it just returns an empty file named sample-data.



      In contrast to curl, however, wget works well returning a file containing proper contents.



      wget https://logz.io/sample-data 


      What have I missed with curl?









      share|improve this question













      share|improve this question




      share|improve this question








      edited May 15 at 11:37









      heemayl

      63.6k8126202




      63.6k8126202










      asked May 15 at 11:07









      user3523935

      120118




      120118




















          1 Answer
          1






          active

          oldest

          votes

















          up vote
          2
          down vote



          accepted










          You've missed to follow redirections with curl as the URL endpoint is redirected (301) to another endpoint (https://s3.amazonaws.com/logzio-elk/apache-daily-access.log); sending a request with HEAD method (-I) to the specified URL:



          % curl -LI https://logz.io/sample-data
          HTTP/1.1 301 Moved Permanently
          ...
          ...
          Location: https://s3.amazonaws.com/logzio-elk/apache-daily-access.log
          ...

          HTTP/1.1 200 OK
          ...
          ...
          Server: AmazonS3


          As curl does not follow HTTP redirections by default, you need to tell curl to do so using the -L/--location option:



          curl -LO https://logz.io/sample-data


          As wget follows redirections by default, you're getting to the eventual URL with wget as-is.






          share|improve this answer






















            Your Answer







            StackExchange.ready(function()
            var channelOptions =
            tags: "".split(" "),
            id: "89"
            ;
            initTagRenderer("".split(" "), "".split(" "), channelOptions);

            StackExchange.using("externalEditor", function()
            // Have to fire editor after snippets, if snippets enabled
            if (StackExchange.settings.snippets.snippetsEnabled)
            StackExchange.using("snippets", function()
            createEditor();
            );

            else
            createEditor();

            );

            function createEditor()
            StackExchange.prepareEditor(
            heartbeatType: 'answer',
            convertImagesToLinks: true,
            noModals: false,
            showLowRepImageUploadWarning: true,
            reputationToPostImages: 10,
            bindNavPrevention: true,
            postfix: "",
            onDemand: true,
            discardSelector: ".discard-answer"
            ,immediatelyShowMarkdownHelp:true
            );



            );








             

            draft saved


            draft discarded


















            StackExchange.ready(
            function ()
            StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2faskubuntu.com%2fquestions%2f1036484%2fcurl-o-stores-an-empty-file-though-wget-works-well%23new-answer', 'question_page');

            );

            Post as a guest






























            1 Answer
            1






            active

            oldest

            votes








            1 Answer
            1






            active

            oldest

            votes









            active

            oldest

            votes






            active

            oldest

            votes








            up vote
            2
            down vote



            accepted










            You've missed to follow redirections with curl as the URL endpoint is redirected (301) to another endpoint (https://s3.amazonaws.com/logzio-elk/apache-daily-access.log); sending a request with HEAD method (-I) to the specified URL:



            % curl -LI https://logz.io/sample-data
            HTTP/1.1 301 Moved Permanently
            ...
            ...
            Location: https://s3.amazonaws.com/logzio-elk/apache-daily-access.log
            ...

            HTTP/1.1 200 OK
            ...
            ...
            Server: AmazonS3


            As curl does not follow HTTP redirections by default, you need to tell curl to do so using the -L/--location option:



            curl -LO https://logz.io/sample-data


            As wget follows redirections by default, you're getting to the eventual URL with wget as-is.






            share|improve this answer


























              up vote
              2
              down vote



              accepted










              You've missed to follow redirections with curl as the URL endpoint is redirected (301) to another endpoint (https://s3.amazonaws.com/logzio-elk/apache-daily-access.log); sending a request with HEAD method (-I) to the specified URL:



              % curl -LI https://logz.io/sample-data
              HTTP/1.1 301 Moved Permanently
              ...
              ...
              Location: https://s3.amazonaws.com/logzio-elk/apache-daily-access.log
              ...

              HTTP/1.1 200 OK
              ...
              ...
              Server: AmazonS3


              As curl does not follow HTTP redirections by default, you need to tell curl to do so using the -L/--location option:



              curl -LO https://logz.io/sample-data


              As wget follows redirections by default, you're getting to the eventual URL with wget as-is.






              share|improve this answer
























                up vote
                2
                down vote



                accepted







                up vote
                2
                down vote



                accepted






                You've missed to follow redirections with curl as the URL endpoint is redirected (301) to another endpoint (https://s3.amazonaws.com/logzio-elk/apache-daily-access.log); sending a request with HEAD method (-I) to the specified URL:



                % curl -LI https://logz.io/sample-data
                HTTP/1.1 301 Moved Permanently
                ...
                ...
                Location: https://s3.amazonaws.com/logzio-elk/apache-daily-access.log
                ...

                HTTP/1.1 200 OK
                ...
                ...
                Server: AmazonS3


                As curl does not follow HTTP redirections by default, you need to tell curl to do so using the -L/--location option:



                curl -LO https://logz.io/sample-data


                As wget follows redirections by default, you're getting to the eventual URL with wget as-is.






                share|improve this answer














                You've missed to follow redirections with curl as the URL endpoint is redirected (301) to another endpoint (https://s3.amazonaws.com/logzio-elk/apache-daily-access.log); sending a request with HEAD method (-I) to the specified URL:



                % curl -LI https://logz.io/sample-data
                HTTP/1.1 301 Moved Permanently
                ...
                ...
                Location: https://s3.amazonaws.com/logzio-elk/apache-daily-access.log
                ...

                HTTP/1.1 200 OK
                ...
                ...
                Server: AmazonS3


                As curl does not follow HTTP redirections by default, you need to tell curl to do so using the -L/--location option:



                curl -LO https://logz.io/sample-data


                As wget follows redirections by default, you're getting to the eventual URL with wget as-is.







                share|improve this answer














                share|improve this answer



                share|improve this answer








                edited May 15 at 11:34

























                answered May 15 at 11:29









                heemayl

                63.6k8126202




                63.6k8126202






















                     

                    draft saved


                    draft discarded


























                     


                    draft saved


                    draft discarded














                    StackExchange.ready(
                    function ()
                    StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2faskubuntu.com%2fquestions%2f1036484%2fcurl-o-stores-an-empty-file-though-wget-works-well%23new-answer', 'question_page');

                    );

                    Post as a guest













































































                    Popular posts from this blog

                    pylint3 and pip3 broken

                    Missing snmpget and snmpwalk

                    How to enroll fingerprints to Ubuntu 17.10 with VFS491