Closed babaMar closed 5 years ago
@babaMar Can you report this issue to the ElasticMQ project? They can help you better.
@vsouza it works if I use directly ElasticMQ container, maybe need to pull the latest version in your Dockerfile?
@babaMar Can you test and get back here with an update to us?
it works correctly.
The following code:
gives a different response from the one given when using a real AWS resource:
{'ResponseMetadata': {'RequestId': '00000000-0000-0000-0000-000000000000', 'HTTPStatusCode': 200, 'HTTPHeaders': {'server': 'akka-http/10.1.3', 'date': 'Wed, 17 Apr 2019 09:48:34 GMT', 'content-type': 'text/plain; charset=UTF-8', 'content-length': '356'}, 'RetryAttempts': 0}}
real-resource response: