-
Notifications
You must be signed in to change notification settings - Fork 110
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
error 503 without "Accept : */*" header #92
Comments
Thank you @michelelazzeri! I've been banging my head against the wall as to why I keep getting those "Website Temporarily Unavailable" HTML response from Amazon for the past few days. I consider this a very serious issue on Amazon's side, and I started getting it in January 23 too. I've tried to use your fork (with the Accept: */* fix) but I still get the same 503 errors. So we share the same problem, but the solution doesn't work for me. Did you change anything else while trying to solve this problem? Maybe the server type or IP? Here's an interesting point: Would appreciate any help trying to nail this issue. |
I try now without "Accept" header and it's works...probably they fix somethings... and probably you occurs in another problems, but the event surely are the same, a new release of pa-api server software. I suggest you to use cURL to test the same HTTP request in your environment and EC2 servers, logging the request done by apac.
I hope this will be useful to you |
Thanks. |
Hi,
starting from 23 January 2018 at 17:30 UTC, node-apac stop to work in our backed. All requests return status "503 service unavailable". Comparing curl requests with node-apac requests we found the problem and fix it adding header Accept (lib/operation-helper.js line 93)
Can anyone confirm this behaviour?
The text was updated successfully, but these errors were encountered: