Getting a 302 in shell but not in browser
up vote
0
down vote
favorite
When I try to get a wget request of page 430 I get a redirect 302.
wget "https://www.zalando.be/kleding/?p=430"
results in
HTTP-verzoek is sent; waiting on answer... 302 Moved Temporarily
Location: /kleding/?p=429 [following...]
--2018-11-10 21:08:57-- https://www.zalando.be/kleding/?p=429
However, when I access the site and push on the button for next page, then it goes to "https://www.zalando.be/kleding/?p=430".
I don't understand how this is possible, can someone elaborate this for me?
Also is it possible to do this in the shell?
html http wget
add a comment |
up vote
0
down vote
favorite
When I try to get a wget request of page 430 I get a redirect 302.
wget "https://www.zalando.be/kleding/?p=430"
results in
HTTP-verzoek is sent; waiting on answer... 302 Moved Temporarily
Location: /kleding/?p=429 [following...]
--2018-11-10 21:08:57-- https://www.zalando.be/kleding/?p=429
However, when I access the site and push on the button for next page, then it goes to "https://www.zalando.be/kleding/?p=430".
I don't understand how this is possible, can someone elaborate this for me?
Also is it possible to do this in the shell?
html http wget
add a comment |
up vote
0
down vote
favorite
up vote
0
down vote
favorite
When I try to get a wget request of page 430 I get a redirect 302.
wget "https://www.zalando.be/kleding/?p=430"
results in
HTTP-verzoek is sent; waiting on answer... 302 Moved Temporarily
Location: /kleding/?p=429 [following...]
--2018-11-10 21:08:57-- https://www.zalando.be/kleding/?p=429
However, when I access the site and push on the button for next page, then it goes to "https://www.zalando.be/kleding/?p=430".
I don't understand how this is possible, can someone elaborate this for me?
Also is it possible to do this in the shell?
html http wget
When I try to get a wget request of page 430 I get a redirect 302.
wget "https://www.zalando.be/kleding/?p=430"
results in
HTTP-verzoek is sent; waiting on answer... 302 Moved Temporarily
Location: /kleding/?p=429 [following...]
--2018-11-10 21:08:57-- https://www.zalando.be/kleding/?p=429
However, when I access the site and push on the button for next page, then it goes to "https://www.zalando.be/kleding/?p=430".
I don't understand how this is possible, can someone elaborate this for me?
Also is it possible to do this in the shell?
html http wget
html http wget
asked Nov 10 at 20:11
Quinten Lootens
106
106
add a comment |
add a comment |
2 Answers
2
active
oldest
votes
up vote
1
down vote
accepted
So it seems that accessing by either wget
or directly writing in the browser's address bar the site's URL for p values greater than 429 will trigger a 302 redirect.
This doesn't happen while pressing the next button because in this way the page content is loaded through AJAX. This is an example of a request being made when clicking the next button: https://www.zalando.be/api/catalog/articles?categories=kleding&limit=84&offset=36036&sort=popularity
I suggest investigating the paging logic for some conditional that may trigger the redirect as an out of range page request protection.
add a comment |
up vote
0
down vote
I was wrong.
It seems that when reloading the page several times, the contents change. The fact that the browser also receives a 302 code when going to www.zalando.be/kleding/?p=430 means there is a server side "problem" with the dynamic content. I don't know how Zalando works, but my best guess is that the popularity sort throws the system off. When the system doesn't know the right amount of entries, it then redirects to page 429 (as evidenced by 431 also redirecting).
This is probably a very temporary redirect because I cannot reproduce the problem.
So you can wget "zalando.be/kleding/?p=430" without getting page 429?
– Quinten Lootens
Nov 10 at 20:45
No, I was actually wrong. Sorry.
– AWhitePelican
Nov 10 at 21:04
add a comment |
2 Answers
2
active
oldest
votes
2 Answers
2
active
oldest
votes
active
oldest
votes
active
oldest
votes
up vote
1
down vote
accepted
So it seems that accessing by either wget
or directly writing in the browser's address bar the site's URL for p values greater than 429 will trigger a 302 redirect.
This doesn't happen while pressing the next button because in this way the page content is loaded through AJAX. This is an example of a request being made when clicking the next button: https://www.zalando.be/api/catalog/articles?categories=kleding&limit=84&offset=36036&sort=popularity
I suggest investigating the paging logic for some conditional that may trigger the redirect as an out of range page request protection.
add a comment |
up vote
1
down vote
accepted
So it seems that accessing by either wget
or directly writing in the browser's address bar the site's URL for p values greater than 429 will trigger a 302 redirect.
This doesn't happen while pressing the next button because in this way the page content is loaded through AJAX. This is an example of a request being made when clicking the next button: https://www.zalando.be/api/catalog/articles?categories=kleding&limit=84&offset=36036&sort=popularity
I suggest investigating the paging logic for some conditional that may trigger the redirect as an out of range page request protection.
add a comment |
up vote
1
down vote
accepted
up vote
1
down vote
accepted
So it seems that accessing by either wget
or directly writing in the browser's address bar the site's URL for p values greater than 429 will trigger a 302 redirect.
This doesn't happen while pressing the next button because in this way the page content is loaded through AJAX. This is an example of a request being made when clicking the next button: https://www.zalando.be/api/catalog/articles?categories=kleding&limit=84&offset=36036&sort=popularity
I suggest investigating the paging logic for some conditional that may trigger the redirect as an out of range page request protection.
So it seems that accessing by either wget
or directly writing in the browser's address bar the site's URL for p values greater than 429 will trigger a 302 redirect.
This doesn't happen while pressing the next button because in this way the page content is loaded through AJAX. This is an example of a request being made when clicking the next button: https://www.zalando.be/api/catalog/articles?categories=kleding&limit=84&offset=36036&sort=popularity
I suggest investigating the paging logic for some conditional that may trigger the redirect as an out of range page request protection.
answered Nov 10 at 22:25
Dan D.
2447
2447
add a comment |
add a comment |
up vote
0
down vote
I was wrong.
It seems that when reloading the page several times, the contents change. The fact that the browser also receives a 302 code when going to www.zalando.be/kleding/?p=430 means there is a server side "problem" with the dynamic content. I don't know how Zalando works, but my best guess is that the popularity sort throws the system off. When the system doesn't know the right amount of entries, it then redirects to page 429 (as evidenced by 431 also redirecting).
This is probably a very temporary redirect because I cannot reproduce the problem.
So you can wget "zalando.be/kleding/?p=430" without getting page 429?
– Quinten Lootens
Nov 10 at 20:45
No, I was actually wrong. Sorry.
– AWhitePelican
Nov 10 at 21:04
add a comment |
up vote
0
down vote
I was wrong.
It seems that when reloading the page several times, the contents change. The fact that the browser also receives a 302 code when going to www.zalando.be/kleding/?p=430 means there is a server side "problem" with the dynamic content. I don't know how Zalando works, but my best guess is that the popularity sort throws the system off. When the system doesn't know the right amount of entries, it then redirects to page 429 (as evidenced by 431 also redirecting).
This is probably a very temporary redirect because I cannot reproduce the problem.
So you can wget "zalando.be/kleding/?p=430" without getting page 429?
– Quinten Lootens
Nov 10 at 20:45
No, I was actually wrong. Sorry.
– AWhitePelican
Nov 10 at 21:04
add a comment |
up vote
0
down vote
up vote
0
down vote
I was wrong.
It seems that when reloading the page several times, the contents change. The fact that the browser also receives a 302 code when going to www.zalando.be/kleding/?p=430 means there is a server side "problem" with the dynamic content. I don't know how Zalando works, but my best guess is that the popularity sort throws the system off. When the system doesn't know the right amount of entries, it then redirects to page 429 (as evidenced by 431 also redirecting).
This is probably a very temporary redirect because I cannot reproduce the problem.
I was wrong.
It seems that when reloading the page several times, the contents change. The fact that the browser also receives a 302 code when going to www.zalando.be/kleding/?p=430 means there is a server side "problem" with the dynamic content. I don't know how Zalando works, but my best guess is that the popularity sort throws the system off. When the system doesn't know the right amount of entries, it then redirects to page 429 (as evidenced by 431 also redirecting).
This is probably a very temporary redirect because I cannot reproduce the problem.
edited Nov 10 at 21:13
answered Nov 10 at 20:30
AWhitePelican
714
714
So you can wget "zalando.be/kleding/?p=430" without getting page 429?
– Quinten Lootens
Nov 10 at 20:45
No, I was actually wrong. Sorry.
– AWhitePelican
Nov 10 at 21:04
add a comment |
So you can wget "zalando.be/kleding/?p=430" without getting page 429?
– Quinten Lootens
Nov 10 at 20:45
No, I was actually wrong. Sorry.
– AWhitePelican
Nov 10 at 21:04
So you can wget "zalando.be/kleding/?p=430" without getting page 429?
– Quinten Lootens
Nov 10 at 20:45
So you can wget "zalando.be/kleding/?p=430" without getting page 429?
– Quinten Lootens
Nov 10 at 20:45
No, I was actually wrong. Sorry.
– AWhitePelican
Nov 10 at 21:04
No, I was actually wrong. Sorry.
– AWhitePelican
Nov 10 at 21:04
add a comment |
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%2fstackoverflow.com%2fquestions%2f53243001%2fgetting-a-302-in-shell-but-not-in-browser%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