Skip to content
This repository has been archived by the owner on Mar 14, 2021. It is now read-only.

400 Bad Request - Request has expired #161

Open
diggde opened this issue Sep 25, 2017 · 1 comment
Open

400 Bad Request - Request has expired #161

diggde opened this issue Sep 25, 2017 · 1 comment

Comments

@diggde
Copy link

diggde commented Sep 25, 2017

I use your apai-io and everything works fine. At first ... thanks a lot. But in the last time I get an 400 Bad Request Error: Request has expired. Here the error message:

GuzzleHttp\Exception\ClientException: Client error: `GET http://webservices.amazon.de/onca/xml?...` resulted in a `400 Bad Request` response:
<?xml version="1.0"?>
<ItemLookupErrorResponse xmlns="http://ecs.amazonaws.com/doc/2013-08-01/"><Error><Code>RequestExpired</Code><Message>Request has expired. Timestamp date is 2017-09-25T11:50:39Z.</Message></Error><RequestID>fa2c4120-ca6e-4611-98da-9069b71e4e2c</RequestID></ItemLookupErrorResponse>
 in /var/www/admin-interface/library/ApaiIOVendor/guzzlehttp/guzzle/src/Exception/RequestException.php on line 113

There is someting wrong with the timestamps or timezones. How can I set the right timestamp?

Thanks for help!

@ttk
Copy link

ttk commented Jun 5, 2018

I ran into this problem and I fixed it by making sure the system time was properly sync'd with the network time.

Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants