Hi, my query is getting status 302 back since today, and it was working properly for a long time until this morning even. I noticed that HTTPS will be enforced, but don't know if anything else is changed / need to change from my side. I use findItemsAdvanced, and just filter for category, keyword and country. Does anyone else having similar problem? What do I need to change? Thanks!
Of the 50 people following this question, is anyone else seeing this too? It's weird that there wouldn't be more noise around this: eBay search API failing.... unless the OP and I are the only people seeing this? Please chime in, anyone. Thanks.
Working OK here. I don't see anything related to https. Provide useful information if you want help, such as a sample call and the error response. 302 is not a documented Finding API error. If the API is returning that error, there should be an error node in the response with more details. But 302 is a HTTP redirect status code. It is not an error, it is a response that provides a new URL to use. If you aren't following redirects properly, you will see this status code and a URL to follow. If your GET request works in a browser, then it's some issue in your code. Stable code can go bad if a system update changed default behavior or introduced a bug in a library or other underlying code.
Anyone with this issue: If you happen to be using cURL to make your API calls, be sure to set the option to follow 301/302 redirects -- set CURLOPT_FOLLOWLOCATION to TRUE. Also check: there's another option for max # of hops on the redirect, and perhaps other tweaks as well. It's in the cURL docs.
By the way, found this: https://airbrake.io/blog/http-errors/302-found The explanation suggests something is wrong w eBay's servers -- not something any of us are doing wrong. The explanation suggests some configuration issue w. eBay's Apache or nginx and goes thru a list of server-debugging steps. While it's reasonable that maybe there's some end-user coding tricks that could help work around, it's my impression from reading the explanation that eBay servers should not be throwing 302s that user code should then dance around. How does one make eBay aware of this? THx
302's are normal. They are used for redirecting requests to the proper resource. That article's claim that "302 Found indicates that something has gone wrong within the server of your application, we can largely disregard the client side of things." is complete nonsense. The link you posted is not working at all. Post it in a code block, it may be damaged by the forum. It gives a 302 to an eBay error page. Have you looked at the response you get in the browser console? Removing the callback parameters lets it go thru. Given that the website is completely rejecting it, this link either wasn't working for months or eBay recently changed the handler. Look to your jQuery and browser. You may be getting an issue related to a cross protocol switch, CORS, etc. The message indicates a cross protocol downgrade issue. Some jQuery versions had trouble with down-grading from https to http. If the 302 is redirecting to http, it could be breaking things. There are workarounds. You may not need the callback parameter. Use jsonp mode. You'll have to post the jquery code, a clean request link, and the 302 response contents to continue.