Single instance HTTP Server using new Ethernet Interface.
Dependents: EthHTTPServer if201410_section5 _PE2E_12-04_EthernetInterfaceServer MGAS_GR_Peach ... more
Fork of WiFlyHTTPServer by
Desciprtion of the library
Overview
This is an HTTPServer library using the new MBED EthernetInterface library. It allows you to :
- serve files from any file System
- use Remote procedure calls
- extend the HTTPServer functionality according to your needs, using the provided handler classes or writing new classes. The following sections will give you a brief overview of how to use the library.
Usage description
You can use the library as file server, as RPC server or a combination of both. You can even define your own behaviour by deriving from one of the classes provided.
Use as file server
You may want to look at my sample application which allows you to serve files from the internal local storage of the mbed with no modifcation of the code :
Very simple example application
#include "mbed.h" #include "HTTPServer.h" #include "FsHandler.h" #include "LocalFileSystem.h" // Use LED1 to indicate that the main loop is still executing DigitalOut myled(LED1); // Use the serial connection 'pc' to dump debug information Serial pc(USBTX, USBRX, "pc"); // Instantiate a HTTPServer to handle incoming requests HTTPServer svr; // Instantiate a local file system handler named 'local' which will be used later to access files on the mbed. LocalFileSystem local("local"); int main() { pc.baud(460800); HTTPFsRequestHandler::mount("/local/", "/"); svr.addHandler<HTTPFsRequestHandler>("/"); if (!svr.start()) { error("Server not starting !"); exit(0); } while(1) { svr.poll(); myled = 1; wait(0.2); myled = 0; wait(0.2); } }
Another alternative is to provide the EthernetInterface library to the HTTPServer library. This may be useful in case you need to perform other tasks with your internet connection. In this case it is necessary that you initialize the EthernetInterface and perform the connection prior to calling the start() method. Here is the example :
Sample application with re-use of existing EthernetInterface object
#include "mbed.h" #include "HTTPServer.h" #include "FsHandler.h" #include "LocalFileSystem.h" #include "EthernetInterface.h" // Use LED1 to indicate that the main loop is still executing DigitalOut myled(LED1); // Use the serial connection 'pc' to dump debug information Serial pc(USBTX, USBRX, "pc"); // Instantiate a HTTPServer to handle incoming requests HTTPServer svr; // Instantiate a local file system handler named 'local' which will be used later to access files on the mbed. LocalFileSystem local("local"); // Create the EthernetInterface. This is optional, please see the documentation of HTTP Server's start method. EthernetInterface eth; int main() { pc.baud(460800); HTTPFsRequestHandler::mount("/local/", "/"); svr.addHandler<HTTPFsRequestHandler>("/"); // Initialize the EthernetInterface and initiate a connection using DHCP. eth.init(); eth.connect(); // *** // TODO: Perform other Tasks using the ethernet connection here. // **** // Now start the server on port 80. if (!svr.start(80, ð)) { error("Server not starting !"); exit(0); } // The whole server activity is performed in this Loop. You can also put it into a separate RTOS Task and let it run there all the time. while(1) { svr.poll(); myled = 1; wait(0.2); myled = 0; wait(0.2); } }
Use as remote procedure call (RPC) server
To access objects or resources via HTTP you can make use of the RPC functionality. Each object that shall be accessible via HTTP needs to be registered before use. Here is an example which Registers the DigitalOut class for use over RPC :
RPC usage over HTTPServer
#include "mbed.h" #include "HTTPServer.h" #include "RpcHandler.h" #include "mbed_rpc.h" // Use LED1 to indicate that the main loop is still executing DigitalOut myled(LED1); // Use the serial connection 'pc' to dump debug information Serial pc(USBTX, USBRX, "pc"); // Instantiate a HTTPServer to handle incoming requests HTTPServer svr; int main() { pc.baud(460800); RPC::add_rpc_class<RpcDigitalOut>(); svr.addHandler<HTTPRpcRequestHandler>("/RPC"); if (!svr.start()) { error("Server not starting !"); exit(0); } while(1) { svr.poll(); myled = 1; wait(0.2); myled = 0; wait(0.2); } }
And using the above code, enter the following in the address field of your browser :
http://<your_mbed_ip>/RPC/DigitalOut/new LED4 myled4
- - > to create a new object of type DigitalOut on pin LED4 which can be referred to as 'myled4'.
and
http://<your_mbed_ip>/RPC/myled4/write 1
- - > to switch on the LED4.
Of course it is possible to Register your own objects with the standard MBED RPC functionality.
All the above Scenarios are implemented in a sample application, which will allow you to try out the functionality with basically no changes. If you want to try out the HTTP file Server, it is of course helpful to upload an html file to your MBED local storage.
Here is the sample application :
Import programEthHTTPServer
Working sample implementation for the EthernetInterface HTTPServer.
Future plans
Currently I am not considering to further extend this library. However, if someone needs extensions to this library, I will consider implementing them. Of course I will be taking care of bugfixes.
Known issues
Please note that the current implementation of the EthernetInterface seems to have an issue which results in unresponsive behaviour of the Sockets in some situations. This odd behaviour has not only been reported on my HTTPServer but also on other components using the EthernetInterface library.
HTTPRequestHandler.h
- Committer:
- leihen
- Date:
- 2013-08-17
- Revision:
- 16:cc3f5c53d0d5
- Parent:
- 12:ba81cc117fb6
File content as of revision 16:cc3f5c53d0d5:
/* HTTPRequestHandler.h */ /* Copyright (c) 2013 Henry Leinen (henry[dot]leinen [at] online [dot] de) Permission is hereby granted, free of charge, to any person obtaining a copy of this software and associated documentation files (the "Software"), to deal in the Software without restriction, including without limitation the rights to use, copy, modify, merge, publish, distribute, sublicense, and/or sell copies of the Software, and to permit persons to whom the Software is furnished to do so, subject to the following conditions: The above copyright notice and this permission notice shall be included in all copies or substantial portions of the Software. THE SOFTWARE IS PROVIDED "AS IS", WITHOUT WARRANTY OF ANY KIND, EXPRESS OR IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF MERCHANTABILITY, FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT. IN NO EVENT SHALL THE AUTHORS OR COPYRIGHT HOLDERS BE LIABLE FOR ANY CLAIM, DAMAGES OR OTHER LIABILITY, WHETHER IN AN ACTION OF CONTRACT, TORT OR OTHERWISE, ARISING FROM, OUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN THE SOFTWARE. */ #ifndef __HTTPREQUESTHANDLER_H__ #define __HTTPREQUESTHANDLER_H__ #include "mbed.h" #include "HTTPConnection.h" #include <map> typedef std::map<const char*,const char*> HTTPHeaders; typedef enum { HTTP_Continue = 100, // 100 HTTP_SwitchingProtocols = 101, // 101 HTTP_Ok = 200, // 200 HTTP_Created = 201, // 201 HTTP_Accepted = 202, // 202 HTTP_NonAuthoritativeInformation = 203, // 203 HTTP_NoContent = 204, // 204 HTTP_ResetContent = 205, // 205 HTTP_PartialContent = 206, // 206 HTTP_MultipleChoices = 300, // 300 HTTP_MovedPermanently = 301, // 301 HTTP_Found = 302, // 302 HTTP_SeeOther = 303, // 303 HTTP_NotModified = 304, // 304 HTTP_UseProxy = 305, // 305 HTTP_TemporaryRedirect = 307, // 307 HTTP_BadRequest = 400, // 400 HTTP_Unauthorized = 401, // 401 HTTP_PaymentRequired = 402, // 402 HTTP_Forbidden = 403, // 403 HTTP_NotFound = 404, // 404 HTTP_MethodNotAllowed = 405, // 405 HTTP_NotAcceptable = 406, // 406 HTTP_ProxyAuthRequired = 407, // 407 HTTP_RequestTimeOut = 408, // 408 HTTP_Conflict = 409, // 409 HTTP_Gone = 410, // 410 HTTP_LengthRequired = 411, // 411 HTTP_PreconditionFailed = 412, // 412 HTTP_RequestEntityTooLarge = 413, // 413 HTTP_RequestURITooLarge = 414, // 414 HTTP_UnsupportedMediaType = 415, // 415 HTTP_RequestedRangeNotSatisfiable = 416, // 416 HTTP_ExpectationFailed = 417, // 417 HTTP_InternalServerError = 500, // 500 HTTP_NotImplemented = 501, // 501 HTTP_BadGateway = 502, // 502 HTTP_ServiceUnavailable = 503, // 503 HTTP_GatewayTimeout = 504, // 504 HTTP_HTTPVersionNotSupported = 505, // 505 } HTTPResponseCode; /** class HTTPRequestHandler is the base class for HTTP Handler request implementations. * */ class HTTPRequestHandler { protected: HTTPConnection::HTTPMessage& msg; TCPSocketConnection& tcp; public: /** Constructor for HTTPRequestHandler objects. */ HTTPRequestHandler(HTTPConnection::HTTPMessage&, TCPSocketConnection&); /** Destructor for HTTPRequestHandler objects. */ virtual ~HTTPRequestHandler(); /** Handler function which will be used by the HTTPServer to serve requests. * The default version of this function will dispatch respective handler member * functions according to the request type given in the HTTPMessage object. * The list of possible functions dispatched is : * * handleGetRequest * * handlePostRequest * * handlePutRequest */ virtual void handleRequest(); /** Handler function which will handle errors and return errors correctly * @param errorCode : The error code returned by the HTTP Server to represent the error condition. * @param msg : Request Message information. * @param tcp : The socket which represents the active connection to the client. */ virtual void handleError(int errorCode, HTTPHeaders* header = NULL); /** Function sends the response header which consists of the return code and the headers section * the response header also contains the length (in bytes) of the body. You need to send the body * right after calling this function. Please note that you do not need to consider the terminating * CR+LF after your last CR+LF. This will be sent automatically once \c endResponse is called. Also * the Length given in \c nLen does not need to consider this additional chars. It will also be * automatically added in \c startResponse. if you need to change the headers, please do NOT * specify the \c Content-Length Header. This is done automatically be the function. */ void startResponse(int returnCode, long nLen, HTTPHeaders* header = NULL); void processResponse(int nLen, char* body ); void endResponse(); protected: /** Handler function to serve GET requests. Download ressource from server from \c uri location. */ virtual int handleGetRequest() = 0; /** Handler function to serve PUT requests. Upload ressource to server to \c uri location. */ virtual int handlePutRequest() = 0; /** Handler function to serve POST requests. Send data to webserver. Can also be appended to uri. */ virtual int handlePostRequest() = 0; void getStandardHeaders(HTTPHeaders& header, const char* fext = NULL); }; #endif // __HTTPREQUESTHANDLER_H__