GET via wget or cURL gives a limited response
I'm bumping my head on a simple HTTP GET request.
Using a tool like Postman, I'm getting the full and expected response (an over 1 thousand of lines xml document long, displaying the details of my 60 albums)
For this GET request, I provide:
- 4 parameters embedded in the url
- The default header "Content-Type: application/x-www-form-urlencoded"
- 13 cookies to secure my identity
With using wget however, I get only a 505 lines long xml document. As far as I know, I do provide the same cookies, same parameters and header.
wget -o logfile.log -O response.xml --load-cookies cookies.txt https://app.viewbook.com/albums/?sort=date&order=desc&page=1&per_page=500
The "response.xml" I get is a well-formed xml document, but with only 25 albums, 505 lines long:
I was thinking there might be a built-in limitation within wget, so I tried with curl
Using curl, I get exactly the same 25 limited albums, 505 lines long xml response:
curl -D filelog.log -o response.xml -H "Content-Type: application/x-www-form-urlencoded" -b "cookie1=val1; cookie2=val2; cookie3=val3..." https://app.viewbook.com/albums/?sort=date&order=desc&page=1&per_page=500
I'm out of ideas why both wget and curl - while not totally failing - don't give the same complete result I get with the Postman tool.
Am I missing some parameters during my GET call?
Where does this limited length response could come from?
curl wget http
asked 39 mins ago
YoricYoric
1084
add a comment |
I'm bumping my head on a simple HTTP GET request.
Using a tool like Postman, I'm getting the full and expected response (an over 1 thousand of lines xml document long, displaying the details of my 60 albums)
For this GET request, I provide:
- 4 parameters embedded in the url
- The default header "Content-Type: application/x-www-form-urlencoded"
- 13 cookies to secure my identity
With using wget however, I get only a 505 lines long xml document. As far as I know, I do provide the same cookies, same parameters and header.
wget -o logfile.log -O response.xml --load-cookies cookies.txt https://app.viewbook.com/albums/?sort=date&order=desc&page=1&per_page=500
The "response.xml" I get is a well-formed xml document, but with only 25 albums, 505 lines long:
I was thinking there might be a built-in limitation within wget, so I tried with curl
Using curl, I get exactly the same 25 limited albums, 505 lines long xml response:
curl -D filelog.log -o response.xml -H "Content-Type: application/x-www-form-urlencoded" -b "cookie1=val1; cookie2=val2; cookie3=val3..." https://app.viewbook.com/albums/?sort=date&order=desc&page=1&per_page=500
I'm out of ideas why both wget and curl - while not totally failing - don't give the same complete result I get with the Postman tool.
Am I missing some parameters during my GET call?
Where does this limited length response could come from?
curl wget http
asked 39 mins ago
YoricYoric
1084
add a comment |
I'm bumping my head on a simple HTTP GET request.
Using a tool like Postman, I'm getting the full and expected response (an over 1 thousand of lines xml document long, displaying the details of my 60 albums)
For this GET request, I provide:
- 4 parameters embedded in the url
- The default header "Content-Type: application/x-www-form-urlencoded"
- 13 cookies to secure my identity
With using wget however, I get only a 505 lines long xml document. As far as I know, I do provide the same cookies, same parameters and header.
wget -o logfile.log -O response.xml --load-cookies cookies.txt https://app.viewbook.com/albums/?sort=date&order=desc&page=1&per_page=500
The "response.xml" I get is a well-formed xml document, but with only 25 albums, 505 lines long:
I was thinking there might be a built-in limitation within wget, so I tried with curl
Using curl, I get exactly the same 25 limited albums, 505 lines long xml response:
curl -D filelog.log -o response.xml -H "Content-Type: application/x-www-form-urlencoded" -b "cookie1=val1; cookie2=val2; cookie3=val3..." https://app.viewbook.com/albums/?sort=date&order=desc&page=1&per_page=500
I'm out of ideas why both wget and curl - while not totally failing - don't give the same complete result I get with the Postman tool.
Am I missing some parameters during my GET call?
Where does this limited length response could come from?
curl wget http
asked 39 mins ago
YoricYoric
1084
I'm bumping my head on a simple HTTP GET request.
Using a tool like Postman, I'm getting the full and expected response (an over 1 thousand of lines xml document long, displaying the details of my 60 albums)
For this GET request, I provide:
- 4 parameters embedded in the url
- The default header "Content-Type: application/x-www-form-urlencoded"
- 13 cookies to secure my identity
With using wget however, I get only a 505 lines long xml document. As far as I know, I do provide the same cookies, same parameters and header.
wget -o logfile.log -O response.xml --load-cookies cookies.txt https://app.viewbook.com/albums/?sort=date&order=desc&page=1&per_page=500
The "response.xml" I get is a well-formed xml document, but with only 25 albums, 505 lines long:
I was thinking there might be a built-in limitation within wget, so I tried with curl
Using curl, I get exactly the same 25 limited albums, 505 lines long xml response:
curl -D filelog.log -o response.xml -H "Content-Type: application/x-www-form-urlencoded" -b "cookie1=val1; cookie2=val2; cookie3=val3..." https://app.viewbook.com/albums/?sort=date&order=desc&page=1&per_page=500
I'm out of ideas why both wget and curl - while not totally failing - don't give the same complete result I get with the Postman tool.
Am I missing some parameters during my GET call?
Where does this limited length response could come from?
curl wget http
curl wget http
asked 39 mins ago
YoricYoric
1084
asked 39 mins ago
YoricYoric
1084
edited 1 min ago
Yoric
asked 39 mins ago
YoricYoric
1084
asked 39 mins ago
YoricYoric
1084
asked 39 mins ago
YoricYoric
1084
1084
add a comment |
add a comment |
0
active
oldest
votes
Your Answer
StackExchange.ready(function() {
var channelOptions = {
tags: "".split(" "),
id: "106"
};
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',
autoActivateHeartbeat: false,
convertImagesToLinks: false,
noModals: true,
showLowRepImageUploadWarning: true,
reputationToPostImages: null,
bindNavPrevention: true,
postfix: "",
imageUploader: {
brandingHtml: "Powered by u003ca class="icon-imgur-white" href="https://imgur.com/"u003eu003c/au003e",
contentPolicyHtml: "User contributions licensed under u003ca href="https://creativecommons.org/licenses/by-sa/3.0/"u003ecc by-sa 3.0 with attribution requiredu003c/au003e u003ca href="https://stackoverflow.com/legal/content-policy"u003e(content policy)u003c/au003e",
allowUrls: true
},
onDemand: true,
discardSelector: ".discard-answer"
,immediatelyShowMarkdownHelp:true
});
}
});
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
StackExchange.ready(
function () {
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2funix.stackexchange.com%2fquestions%2f500532%2fget-via-wget-or-curl-gives-a-limited-response%23new-answer', 'question_page');
}
);
Post as a guest
Required, but never shown
0
active
oldest
votes
0
active
oldest
votes
active
oldest
votes
active
oldest
votes
Thanks for contributing an answer to Unix & Linux Stack Exchange!
- Please be sure to answer the question. Provide details and share your research!
But avoid …
- Asking for help, clarification, or responding to other answers.
- Making statements based on opinion; back them up with references or personal experience.
To learn more, see our tips on writing great answers.
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
StackExchange.ready(
function () {
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2funix.stackexchange.com%2fquestions%2f500532%2fget-via-wget-or-curl-gives-a-limited-response%23new-answer', 'question_page');
}
);
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
