|0.8.5||Oct 17, 2022|
|0.8.3||Aug 30, 2022|
|0.7.4||Jun 8, 2022|
|0.7.0||Mar 1, 2022|
|0.0.8||Dec 16, 2017|
#33 in HTTP server
168 downloads per month
Simple and configurable command-line HTTP server
cargo install http-server
Verify successful installation.
Expect the following output:
USAGE: http-server [FLAGS] [OPTIONS] [root-dir] FLAGS: --cors Enable Cross-Origin Resource Sharing allowing any origin --graceful-shutdown Waits for all requests to fulfill before shutting down the server --gzip Enable GZip compression for HTTP Responses --help Prints help information --logger Prints HTTP request and response details to stdout --tls Enables HTTPS serving using TLS -V, --version Prints version information -v, --verbose Turns on stdout/stderr logging OPTIONS: -c, --config <config> Path to TOML configuration file -h, --host <host> Host (IP) to bind the server [default: 127.0.0.1] --password <password> Specifies password for basic authentication -p, --port <port> Port to bind the server [default: 7878] --proxy <proxy> Proxy requests to the provided URL --tls-cert <tls-cert> Path to the TLS Certificate [default: cert.pem] --tls-key <tls-key> Path to the TLS Key [default: key.rsa] --tls-key-algorithm <tls-key-algorithm> Algorithm used to generate certificate key [default: rsa] --username <username> Specifies username for basic authentication ARGS: <root-dir> Directory to serve files from [default: ./]
If you find this output is out of date, don't hesitate to open a PR here.
When running the server with no options or flags provided, a set of default configurations will be used. You can always change this behavior by either creating your own config with the Configuration TOML file or by providing CLI arguments described in the usage section.
|Host||Address to bind the server||
|Port||Port to bind the server||
|Root Directory||The directory to serve files from||
|File Explorer UI||A File Explorer UI for the directory configured as the Root Directory||Enabled|
|Configuration File||Specifies a configuration file. Example||Disabled|
|HTTPS (TLS)||HTTPS Secure connection configuration. Refer to TLS (HTTPS) reference||Disabled|
|CORS||Cross-Origin-Resource-Sharing headers support. Refer to CORS reference||Disabled|
|Compression||GZip compression for HTTP Response Bodies. Refer to Compression reference||Disabled|
|Verbose||Print server details when running. This doesn't include any logging capabilities.||Disabled|
|Basic Authentication||Authorize requests using Basic Authentication. Refer to Basic Authentication||Disabled|
|Logger||Prints HTTP request and response details to stdout||Disabled|
http-server [FLAGS] [OPTIONS] [root-dir]
Flags are provided without any values. For example:
|Cross-Origin Resource Sharing||N/A||
||Enable Cross-Origin Resource Sharing allowing any origin|
||Enable GZip compression for responses|
||Wait for all requests to be fulfilled before shutting down the server|
||Print help information|
||Print HTTP request and response details to stdout|
||Print version information|
||Print output to console|
Options receive a value and support default values as well.
http-server --host 127.0.0.1
||Address to bind the server||
||Port to bind the server||
||Configuration file. Example||N/A|
||Enable TLS for HTTPS connections. Requires a Certificate and Key. Reference||N/A|
||Path to TLS certificate file. Depends on
||Path to TLS key file. Depends on
|TLS Key Algorithm||N/A||
||Algorithm used to generate certificate key. Depends on
||Username to validate using basic authentication||N/A|
||Password to validate using basic authentication. Depends on
||Proxy requests to the provided URL||N/A|
This HTTP Proxy supports different Request Handlers which determine how each incoming HTTP request is handled. They can't be combined, you must choose one based on your needs.
- File Server default
File Server Handler
Serves files from the provided directory. Navigation is scoped to the specified directory. If no directory is provided the CWD will be used.
This is the default behavior for the HTTP server.
Proxies requests to the provided URL. The URL provided is used as the base URL for incoming requests.
The following are some relevant details on features supported by this HTTP Server that may be of interest to the user.
Even though compression is supported, by default the server will not compress any HTTP response contents. You must specify the compression configuration you want to use, in the configuration file or on the command line.
As of today the server only supports compression with the GZip algorithm, but
brotli support is also planned.
The following MIME types are never compressed:
The Configuration File's Compression Section
As future support for other compression algorithms is planned, the configuration file already supports compression settings.
[compression] gzip = true
--gzip argument to the server when executing it.
The TLS solution supported for this HTTP Server is built with the rustls crate along with hyper-rustls.
When running with TLS support you will need:
- A certificate
- A matching RSA Private Key for the certificate
A script to generate certificates and keys is available here tls-cert.sh.
This script relies on
openssl, so make sure you have it installed on your system.
http-server as follows:
http-server --tls --tls-cert <PATH TO YOUR CERTIFICATE> --tls-key <PATH TO YOUR KEY> --tls-key-algorithm pkcs8
Cross-Origin Resource Sharing (CORS)
This HTTP Server supports CORS headers out of the box. Based on the headers you want to provide in your HTTP Responses, two different methods for CORS configuration are available.
By providing the
--cors option to
http-server, CORS headers
will be appended to every HTTP Response, allowing any origin.
For more complex configurations, like specifying an origin, a set of allowed HTTP methods and more, you should specify the configuration via the configuration TOML file.
The following example shows all the available options.
[cors] allow_credentials = false allow_headers = ["content-type", "authorization", "content-length"] allow_methods = ["GET", "PATCH", "POST", "PUT", "DELETE"] allow_origin = "example.com" expose_headers = ["*", "authorization"] max_age = 600 request_headers = ["x-app-version"] request_method = "GET"
Basic Authentication is supported to deny requests when credentials are invalid.
You must provide the allowed
password either by using the CLI
--username along with the desired username and
--password along with
the desired password, or by specifying such values through the configuration
[basic_auth] username = "John" password = "Appleseed"
The HTTP Server is able to proxy requests to a specified URL.
When using the proxy, the FileExplorer won't be available, as the proxy is an alternate Request Handler.
The config TOML file can be used to provide proxy configurations:
[proxy] url = "https://example.com"
The following roadmap list features to provide for the version
This roadmap is still open for suggestions. If you find that there's a missing feature in this list, that you would like to work on or expect for the first stable release, please contact the software editors by opening an issue or a discussion.
If you want to contribute to one of these, please make sure there's an issue tracking the feature and ping me. Otherwise open an issue to be assigned and track the progress there.
- Request/Response Logging
- Service Config Loggins
- File Explorer
- Modified Date
- File Size
- Breadcrumb Navigation
- File Upload
- Sort By: File Name
- Sort By: File Size
- Sort By: File Modified Date
- Directories First
- Files First
- HTTPS/TLS Serving
- HTTPS/TLS Support
- Cross Origin Resource Sharing
- Allow Credentials
- Allow Headers
- Allow Methods
- Allow Origin
- Expose Headers
- Max Age
- Request Headers
- Request Methods
- Multiple Origins (#8)
- Cross Origin Resource Sharing
- Cache Control
- Respond with 304 to
- Partial Request
- Standalone Builds
- Development Server
- Live Reload
- URL Configuration
- Basic Authentication
- Graceful Shutdown
In order to create a release you must push a Git tag as follows
git tag -a <version> -m <message>
git tag -a v0.1.0 -m "First release"
Tags must follow semver conventions. Tags must be prefixed with a lowercase
Then push tags as follows:
git push origin main --follow-tags
Every contribution to this project is welcome. Feel free to open a pull request or an issue. Just by using this project you're helping it grow. Thank you!
Distributed under the terms of both the MIT license and the Apache License (Version 2.0)