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 lines xml document, 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"
- 1 cookie containing my session ID, 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 "_accountservice3_session=ZFp6UU..." 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?