This is what the Terminal receives from the Connection Host/web-based App Server in response to a
properly configured page request as outlined above.
Sample:
HTTP/1.1 200 OK
Content-Type: text/plain
Transfer-Encoding: chunked
19
wd*data:@1,1,1,Enter Data%04
(blank line)
Explanation:
Basically, the terminal will read the first line and make sure it includes “100 Continue” or “200 OK” (more
on this below) and then read lines until it finds a blank line (CR/LF alone). If one of the header entries is
Transfer-Encoding: chunked
the terminal will know that the page content (after the blank line that terminates the header) is in “chunked”
format, which is as follows
HTTP/1.1 200 OK
Content-Type: text/plain
Transfer-Encoding: chunked
25
This is the data in the first chunk
1C
and this is the second one
3
con
8
sequence
0
(blank line)
Where xx is the length (hex byte count) of the data chunk on the following line. Content is terminated with a
0 data length and a following blank line. Notice that CR/LF can be included in the data chunks; termination
MUST be a 0 chunk size followed by a blank line (CR/LF only).
If the data format is not chunked, then there will be a line like this in the header:
Content-Length: 1354
After being deciphered from whatever is the sending mode, data from the Host will always look like
wd*data:@1,1,1,Enter Data%04
68
