I believe what's happening is that the response the bot is getting is the same as the one cURL is getting, which is the 301 error, which isn't very helpful in terms of getting Amazon data, obviously. I believe it's a redirect-following error, so I can look into it later.

from amazonmonitor.

Can you give me a short example of what your proxylist looks like? What problem specifically are you having? Like, are the requests failing or something?

Edit: Sorry just read through the debug output a bit more, no need to answer those. Do they work without user/pass authentication? Can you test the Amazon request using the proxy with something like cURL to see what specifically comes back?

from amazonmonitor.

Thank-you for your response.

I'm not getting anything back when doing a curl with or without proxy on that URL. When I try it on amazon.de itself it shows the same thing with or without proxy.
The proxies work with and without user/password yes. Tested both though.
When testing with proxy on for example "https://www.amazon.de/-/en/gp/movers-and-shakers/?ref_=nav_em_ms_0_1_1_4" it works fine with CURL and it downloads some code.

c:\temp>curl https://www.amazon.de/-/en/gp/movers-and-shakers/?ref_=nav_em_ms_0_1_1_4 --proxy 185.250.XX.XXX:8085 --output test.txt
% Total % Received % Xferd Average Speed Time Time Time Current
Dload Upload Total Spent Left Speed
100 41789 0 41789 0 0 41789 0 --:--:-- 0:00:01 --:--:-- 31467

c:\temp>curl amazon.de --proxy 185.250.XX.XXX:8085

301 Moved Permanently

c:\temp>curl amazon.de

301 Moved Permanently

from amazonmonitor.

I can't say I have ever come across this error since my last comment. If this is still an issue, let me know!

from amazonmonitor.