POST request for the Stoker

Intro

This page will describe the POST HTTP request for the Stoker web page.

HTTP Headers

The changes the user makes is passed to the Stoker using the POST method. This means the standard HTTP request is required:

POST /stoker.Post_Handler HTTP/1.0
Content-Type: application/x-www-form-urlencoded
Content-Length: xxx

the-encoded-data

The xxx is replaced by the actual length of the encoded data. The encoded data is the standard pair of "names=values" separated by &'s. This is all pretty much standard HTTP.

Name Fields

There are only five different formats for the name fields:

Format	Description	Value
`naSTOKER_SERIAL_NUMBER`	Change the name	Letters and numbers
`alSTOKER_SERIAL_NUMBER`	Change the alarm type	0, 1, 2
`taSTOKER_SERIAL_NUMBER`	Change the target temp	Number
`thSTOKER_SERIAL_NUMBER`	Change the alarm high temp	Number
`tlSTOKER_SERIAL_NUMBER`	Change the alarm low temp	Number
`swSTOKER_SERIAL_NUMBER`	Change the blower associated with the sensor	Blower serial number

STOKER_SERIAL_NUMBER is the serial number that uniquely identifies the sensor or blower.

Value Fields

The value field for the name depends on the parameter being modified. The name change accepts a string of letters and numbers and other symbols. The temperature value is a value in Fahrenheit.

Alarm value of 0 disables the alarm for the sensor. Alarm value of 1 enables the target alarm. Alarm value of 2 enables the fire alarm.

The value for the swSTOKER_SERIAL_NUMBER must be a valid blower serial number. This associates the sensor and the blower to eachother. The special value of "None" is also accepted. This disassociates the sensor from any blower.

Example 1

To change the name of the sensor with serial number 1234567890 to "Pork Shoulder", the HTTP request would look like:

POST /stoker.Post_Handler HTTP/1.0
Content-Type: application/x-www-form-urlencoded
Content-Length: 25

n1234567890=Pork+Shoulder

Please note a few things:

The CRLF empty line is necessary between the header and the message body.
The length field contains the length of the message body only.
The value field must be properly encoded as defined by the HTML specification. It looks like there are some differences between the generic URL encoding and the URL encoding used specifically for POST requests.

Example 2

To change the name of the sensor with serial number 1234567890 to "Pork Shoulder" and the target temperature to 250.1, the HTTP request would look like:

POST /stoker.Post_Handler HTTP/1.0
Content-Type: application/x-www-form-urlencoded
Content-Length: 44

n1234567890=Pork+Shoulder&ta1234567890=250.1