HTTP Test Server
Programatically create end-points that listen for connections and return pre-defined responses.
- Allows multiple endpoints and simultaneous client connections
- Streaming support
- Helper functions to retrieve data such as request count, number of connected clients and requests metadata
- Automatically allocates free port and close server after use
Examples:
Accept POST requests:
extern crate http_test_server;
use ;
use ;
let server = new.unwrap;
let resource = server.create_resource;
resource
.status
.method
.header
.header
.body;
// request: POST /some-endpoint/new
// HTTP/1.1 201 Created\r\n
// Content-Type: application/json\r\n
// Cache-Control: no-cache\r\n
// \r\n
// { "message": "this is a message" }
Use path and query parameters
extern crate http_test_server;
use ;
use ;
let server = new.unwrap;
let resource = server.create_resource;
resource
.status
.header
.header
.body;
// request: GET /user/abc123?filter=all
// HTTP/1.1 200 Ok\r\n
// Content-Type: application/json\r\n
// Cache-Control: no-cache\r\n
// \r\n
// { "id": "abc123", "filter": "all" }
Expose a persistent stream:
let server = new.unwrap;
let resource = server.create_resource;
resource
.header
.header
.stream
.body;
// ...
resource
.send
.send
.send_line
.close_open_connections;
// request: GET /sub
// HTTP/1.1 200 Ok\r\n
// Content-Type: text/event-stream\r\n
// Cache-Control: no-cache\r\n
// \r\n
// : initial data
// some data some extra data\n
// some extra data with line break\n
Redirects:
let server = new.unwrap;
let resource_redirect = server.create_resource;
let resource_target = server.create_resource;
resource_redirect
.status
.header;
resource_target.body;
// request: GET /original
// HTTP/1.1 303 See Other\r\n
// Location: /new\r\n
// \r\n
Regex URI:
let server = new.unwrap;
let resource = server.create_resource;
// request: GET /hello/8/b/doesntmatter-hehe
// HTTP/1.1 200 Ok\r\n
// \r\n
Check /tests/integration_test.rs for more usage examples.
NOTE: This is not intended to work as a full featured server. For this reason, many validations
and behaviours are not implemented. e.g: A request with Accept header with not supported
Content-Type won't trigger a 406 Not Acceptable.
As this crate was devised to be used in tests, smart behaviours could be confusing and misleading. Having said that, for the sake of convenience, some default behaviours were implemented:
- Server returns
404 Not Foundwhen requested resource was not configured. - Server returns
405 Method Not Allowedwhen trying to reach resource with different method from those configured. - When a resource is created it responds to
GETwith200 Okby default.
License
Licensed under either of
- Apache License, Version 2.0 (LICENSE-APACHE)
- MIT license (LICENSE-MIT)
at your option.
Contribution
Unless you explicitly state otherwise, any contribution intentionally submitted for inclusion in the work by you, as defined in the Apache-2.0 license, shall be dual licensed as above, without any additional terms or conditions.