I have been using ElasticMQ, it is supposed to behave like AWS SQS.
- According to AWS SQS online documentation, any illegal strings that are out of this range #x9 | #xA | #xD | #x20 to #xD7FF | #xE000 to #xFFFD | #x10000 to #x10FFFF, will be rejected.
But when I created an illegal string (only consists of one illegal char), and sent it to ElasticMQ, it was not rejected.
- ElasticMQ did behave strangely though: for this illegal string (one char), the MD5 checksum calculated on the client side was very different from the MD5 checksum returned by ElasticMQ.
Can anyone verify if ElasticMQ is able to reject illegal strings?