An HTTP message consists of a request or status line, header fields and, optionally, a message body. A payload intended for a user program can be included in the query segment of the request line and in the message body. The header fields contain information about the properties of the message.
An HTTP client addresses a service using a URL (see RFC 3986). A URL is structured as follows:
http://example.com:8042/over/there?name=ferret#nose\_/ \______________/ \________/ \_________/ \__/ | | | | |scheme authority path query fragment
With openUTM, the path of a URL always starts with the first slash ("/") after the authority part.
When calling a service of a UTM application via an HTTP request, a user should not specify a fragment of the URL, since many HTTP clients remove the fragment from the request and do not transmit it to the server. In an HTTP response, fragment information is used by the client to interpret the response, for example, to position it on a specific page of a pdf file or on a specific chapter of an HTML message.