sms message structure

, blank line, response body　　Four: Example1. Customer-Side Request ExampleGET/Hello.TXT HTTP/1.1 　　 User-Agent:Curl/7.16. 3 Libcurl/7.16. 3 openssl/0.9.7l Zlib/1.2. 3 host: Www.. COM accept-language: En, mi 2. Server Response Example HTTP/1.1 200OkDate: Mon, 27 Jul 2009 12:28:53GmtServer: Apache 　　 Last-Modified: Wed, 22 Jul 2009 19:15:56 GMT etag: "34aa387-d-1568eb00" accept -ranges: bytes content　　-length: 51vary: accept- encoding content-type : Text/plain 3 output result

Reference: http://www.runoob.com/http/http-messages.html(1) Request Packet structure:First part: Request line (first line of packet) [get/http/1.1]The request line contains three parts:Request Method (Get/post)Request resource Path (content after port number, such as/appname/servlet)Type and version of the ProtocolPart Two: Several message headers (key-value pairs defined by the consortium with special meanings)The style of the

6.1 Global Variables6.2 Compilation preprocessing6.3 Large Program Structure6.1 Global VariablesGlobal variablesVariables defined outside the function are global variablesGlobal variables have global lifetimes and scopesThey have nothing to do with any function.They can be used inside any functionGlobal variable InitializationA global variable that does not initialize will get a value of 0The pointer will get a null valueGlobal variables can only be initialized with values that are known at comp

is transmitted to the card, but some data is returned from the card. The subject of APDU only contains non-empty le fields.Case 3: data is transmitted to the card, but no data is returned from the card. The subjects of APDU include LC and data domains.Case 4: data is transferred to the card and the result of data as a command is returned from the card. The subjects of APDU include LC, data, and Le.Domain. The structure of the response to APDU is

corresponding.There are a lot of analytical methods, which are not mentioned here.Request/Response EntityHTTP request, in addition to the head, there are message entities, in general, the request entity will have some required parameters are put into (for the POST request). For example, the entity can put parameters in the serialized form ( a=1b=2 this), or directly put the form object ( FormData object, upload can be mixed with parameters and files)

, 100 indicates that the server is processing customer requests2XX: Indicates that the request has been successfully received, understood, accepted. Like 200 means the request is successful.3XX: Indicates that the client is redirected to another resource. For example, 301 indicates that this page is permanently transferred to another address; 302 means redirect, the browser automatically jumps to the new connection; 304 indicates that the last document was saved and can continue to use4XX: Reque