sqs-dg-2009-02-01

More documents

Recommendations

Info

Amazon Simple Queue Service Developer GuideStructure of a POST Requestthe signature in the example to be accurate based on the request parameters presented in theexample. The one exception to this is in the instructions for creating Query request signatures.The example there shows a real signature based on a particular AWS Access Key ID we specifyand the request parameters in the example (for more information, see Query RequestAuthentication (p. 23)).In SQS, all parameters except MessageBody always have values that have no spaces. The value youprovide for MessageBody in SendMessage requests can have spaces. In this guide, any exampleSendMessage Query requests with a MessageBody that includes spaces is displayed with the spacesURL encoded (as %20). For clarity, the rest of the URL is not displayed in a URL encoded format.The first line represents the endpoint of the request.This is the resource the request acts on.The precedingexample acts on a queue, so the request's endpoint is the queue's identifier, known as the queue URL.For more details about the queue URL, see Queue URLs (p. 6).After the endpoint is a question mark (?), which separates the endpoint from the parameters. Eachparameter is separated by an ampersand (&).The Action parameter indicates the action to perform (for a list of the actions, see API Actions in theAmazon SQS API Reference). For a list of the other parameters that are common to all Query requests,see Request Parameters Common to All Actions in the Amazon SQS API Reference.Structure of a POST RequestSQS also accepts POST requests. With a POST request, you send the query parameters as a form inthe HTTP request body as described in the following procedure.To create a POST request1. Assemble the query parameter names and values into a form.This means you put the parameters and values together like you would for a GET request (with anampersand separating each name-value pair).The following example shows a SendMessage requestwith the line breaks we use in this guide to make the information easier to read.Action=SendMessage&MessageBody=Your Message Text&AWSAccessKeyId=0GS7553JW74RRM612K02EXAMPLE&Version=2009-02-01&Expires=2008-02-10T12:00:00Z&SignatureVersion=2&SignatureMethod=HmacSHA2562. Form-URL-encode the form according to the Form Submission section of the HTML specification(for more information, go to http://www.w3.org/MarkUp/html-spec/html-spec_toc.html#SEC8.2.1).Action=SendMessage&MessageBody=Your+Message+Text&AWSAccessKeyId=0GS7553JW74RRM612K02EXAMPLE&Version=2009-02-01&Expires=2008-02-10T12%3A00%3A00Z&SignatureVersion=2&SignatureMethod=HmacSHA2563. Add the request signature to the form (for more information, see Query Request Authentication (p. 23)).API Version 2009-02-0115
Amazon Simple Queue Service Developer GuideRelated TopicsAction=SendMessage&MessageBody=Your+Message+Text&AWSAccessKeyId=0GS7553JW74RRM612K02EXAMPLE&Version=2009-02-01&Expires=2008-02-10T12%3A00%3A00Z&SignatureVersion=2&SignatureMethod=HmacSHA256&Signature=lBP67vCvGlDMBQ1dofZxg8E8SUEXAMPLE4. Provide the resulting form as the body of the POST request.5. Include the Content-Type HTTP header with the value set toapplication/x-www-form-urlencoded.The following example shows the final POST request.POST /queue1 HTTP/1.1Host: sqs.us-east-1.amazonaws.comContent-Type: application/x-www-form-urlencodedAction=SendMessage&MessageBody=Your+Message+Text&AWSAccessKeyId=0GS7553JW74RRM612K02EXAMPLE&Version=2009-02-01&Expires=2008-02-10T12%3A00%3A00Z&SignatureVersion=2&SignatureMethod=HmacSHA256&Signature=lBP67vCvGlDMBQ1dofZxg8E8SUEXAMPLESQS requires no other HTTP headers in the request besides Content-Type.The authentication signatureyou provide is the same signature you would provide if you sent a GET request (for information aboutthe signature, see Query Request Authentication (p. 23)).NoteYour HTTP client typically adds other items to the HTTP request as required by the version ofHTTP the client uses. We don't include those additional items in the examples in this guide.Related Topics• Query Request Authentication (p. 23)• Responses (p. 27)API Version 2009-02-0116
Page 1 and 2: Amazon Simple Queue ServiceDevelope
Page 3 and 4: Amazon Simple Queue Service Develop
Page 17: Amazon Simple Queue Service Develop
Page 69 and 70:
Amazon Simple Queue Service Develop
Page 71 and 72:
Page 73 and 74:
Page 75 and 76:
Page 77 and 78:
Page 79 and 80:
Page 81 and 82:
show all

sqs-dg-2009-02-01

Create successful ePaper yourself

Delete template?

Save as template?