WSP UDP
This message flow simulates a WSP Get over UDP (WAP 1.x). The flow is intended to generate simple WSP connection-less traffic between the MN node and the Network Host node.
When control plane protocols are used, the message flow begins after Data Start Delay timer expires. The Client Port and Server Port in the message flow define the ports used for the WSP exchange.
-
The client begins the message sequence by issuing the Get request and the server responds with the content.
In the default configuration, the message flow will repeat once per second while the MN session is active. This assumes that the entire flow can be completed in one second. The flow must complete before the next iteration can begin, even if this results in a slower transaction rate.
Modifying the Message Flow
The encoded fields in the message are shown in red in the diagram above, and the text fields are shown in black.
The WSP Get request is encoded with the following:
-
Transaction ID: 1
-
PDU Type: Get
-
URI Length: 0x13
-
URI: www.dogsandcats.com
-
Accept header: application/vnd.wap.wmlc
-
Accept-Language header: English
The WSP Get response is encoded with the following:
-
Transaction ID: 1
-
PDU Type: Reply
-
Status: 200 OK
-
Headers Length: 1
-
Content-Type header: text/plain
If you modify the URI in the request, the URI Length must also be changed.
You can modify the response content by changing the filler bytes, editing the content, or importing a file to use for the content.
You can specify that random port numbers, in the IANA specified dynamic range of 49152 — 65535, be used by the client by entering a 0 for the Client Port.
More extensive modifications should only be attempted if you are familiar with WSP.