A LCS-Client requests a Location Query Service by issuing an HTTPS POST request towards the LES.
The request line syntax is shown below.
Request-line: POST SP host SP HTTP/1.1 CRLF
The request must include the entity-header Content-length field as part of the request. The message body
of the request will consist of three HTTP post parameters:
• Context – This will contain the authentication details of the client (see chapter 2.4)
• Method – This will identify the method that is to be invoked (consists of the name of the message
being requested)
• Body – This will contain the XML payload for the specified method (see chapter 3)
The use of these parameters will allow an easier migration to SOAP, only minimal changes are required.
This is because these parameters mirror the SOAP header and body sections but do not re-invent SOAP.
Header and body have to correspond with XML and have to be urlencoded. The content-type of the
request has to be "application/x-www-form-urlencoded":
&Context=URLEncoded(HdrElement)&Method=Method&Body=URLEncoded(BodyElement)
"Application/x-www-form-urlencoded" is the default content type. Forms submitted with this content type
must be encoded as follows:
• Control names and values are escaped. Space characters are replaced by `+', and then reserved
characters are escaped as described in "Uniform Resource Locators" (T. Berners-Lee, L. Masinter,
and M. McCahill, December 1994, [RFC1738]), section 2.2: Non-alphanumeric characters are
replaced by `%HH', a percent sign and two hexadecimal digits representing the ASCII code of the
character. Line breaks are represented as "CR LF" pairs (i.e., `%0D%0A').
• The control names/values are listed in the order they appear in the document. The name is separated
from the value by `=' and name/value pairs are separated from each other by `&'.
More information about "application/x-www-form-urlencoding" can be found at http://w3.org/TR/REChtml40-
971218, chapter 17.13.4.
The answer will be included in the message body (see chapters 2.2.5 and 2.2.6) and the Content-length
entity will be set to the length of the answer. The responses have no header part.
Example HdrElement :