sqs-m5
Create successful ePaper yourself
Turn your PDF publications into a flip-book with our unique Google optimized e-Paper software.
Amazon Simple Queue Service Developer Guide<br />
Related Topics<br />
Action=SendMessage<br />
&MessageBody=Your+Message+Text<br />
&AWSAccessKeyId=0GS7553JW74RRM612K02EXAMPLE<br />
&Version=2009-02-01<br />
&Expires=2008-02-10T12%3A00%3A00Z<br />
&SignatureVersion=2<br />
&SignatureMethod=HmacSHA256<br />
&Signature=lBP67vCvGlDMBQ1dofZxg8E8SUEXAMPLE<br />
4. Provide the resulting form as the body of the POST request.<br />
5. Include the Content-Type HTTP header with the value set to<br />
application/x-www-form-urlencoded.<br />
The following example shows the final POST request.<br />
POST /queue1 HTTP/1.1<br />
Host: <strong>sqs</strong>.us-east-1.amazonaws.com<br />
Content-Type: application/x-www-form-urlencoded<br />
Action=SendMessage<br />
&MessageBody=Your+Message+Text<br />
&AWSAccessKeyId=0GS7553JW74RRM612K02EXAMPLE<br />
&Version=2009-02-01<br />
&Expires=2008-02-10T12%3A00%3A00Z<br />
&SignatureVersion=2<br />
&SignatureMethod=HmacSHA256<br />
&Signature=lBP67vCvGlDMBQ1dofZxg8E8SUEXAMPLE<br />
SQS requires no other HTTP headers in the request besides Content-Type.The authentication signature<br />
you provide is the same signature you would provide if you sent a GET request (for information about<br />
the signature, see Query Request Authentication (p. 23)).<br />
Note<br />
Your HTTP client typically adds other items to the HTTP request as required by the version of<br />
HTTP the client uses. We don't include those additional items in the examples in this guide.<br />
Related Topics<br />
• Query Request Authentication (p. 23)<br />
• Responses (p. 27)<br />
API Version 2009-02-01<br />
16