Setting the Socket for HTTP
|Top Previous Next|
How to set the socket for HTTP
Apart from assigning some memory to the TX, RX, and VAR buffers, the following needs to be done to make the socket work in HTTP mode:
In the previous topic, we have already explained that your system should reserve several HTTP sockets. Here is a possible initialization example:
To make sure that the HTTP is working you can create and add to the project a simple static HTTP file. Call this file <index.html>- this is a default file that will be called if no specific file is requested by GET or POST. Here is a static file example:
Launch the browser, type the IP-address of your device, for example: "http://192.168.1.95" and you will get the output "HELLO WORLD!".
Double-duty: non-HTTP and HTTP processing on the same socket
Your HTTP sockets don't have to be exclusively HTTP. You can have them behave differently depending on which listening port the TCP connection is being made to. Here is an example: supposing the setup of your device needs to be effected in two ways- via TELNET or via HTTP. Standard TELNET port is 23, standard HTTP port is 80. Setup your socket like this:
The socket will now be accepting connections both on port 23 and port 80. When connection is made to port 23, the socket will work as a regular data socket, as was described in previous sections. When connection is made to port 80, the socket will automatically switch into the HTTP mode!
There is a property- sock.httpmode- that tells you which mode the socket is in- regular data mode or HTTP. You can even "forcefully" switch any TCP connection into the HTTP mode by setting sock.httpmode= 1- YES. You cannot, however, switch this connection back to the data mode, it will remain in the HTTP mode until termination.