thewawar/simple-http-server

Simple http server in Rust (Windows/Mac/Linux)

View on GitHub ↗Jump to charts ↓

Summary Information

Updated 10 minutes ago
Type:ApplicationCategory(s):Backend FrameworksWeb Development
Added to GitGenius on September 20th, 2026
Created on May 27th, 2017
Open Issues & Pull Requests: 44 (+0)
GitHub issues: Enabled
Number of forks: 219
Total Stargazers: 3,456 (+0)
Total Subscribers: 32 (+0)

Charts & Analytics

Fetching additional details & charts...

Issue Activity (beta)

Open issues: 12
New in 7 days: 0
Closed in 7 days: 0
Avg open age: 799 days
Stale 30+ days: 12
Stale 90+ days: 11

Recent activity

Opened in 7 days: 0
Closed in 7 days: 0
Comments in 7 days: 0
Events in 7 days: 0

Top labels

  • bug (1)
  • enhancement (1)

Most active issues this week

No issue events were indexed in the last 7 days.

Detailed Description

Simple HTTP Server is a static file server written in Rust that runs on Windows, Mac, and Linux.

The tool solves the problem of quickly serving static files and directories over HTTP without complex configuration. It builds on the axum and tokio libraries to provide a lightweight server that handles common web serving scenarios. The implementation includes directory listing with breadcrumb navigation, optional index.html rendering, file upload with CSRF protection, HTTP Basic Auth, cache control headers, gzip and deflate compression, CORS headers, and SPA fallback routing. HTTPS support via PKCS#12 certificates is available as an optional feature that keeps the default binary smaller when disabled.

Developers should choose this tool when they need a quick, self-contained HTTP server for development, testing, or simple static hosting without the overhead of larger web servers. It suits projects that need to serve directories with optional upload capability, single-page applications that require fallback routing, or scenarios where basic authentication is sufficient. The tool is particularly useful for local development and small deployments where a minimal binary size matters.

The project shows consistent maintenance with regular commits addressing bug fixes and feature improvements. Development activity demonstrates responsiveness to user issues and pull requests. The codebase maintains clean separation between core functionality and optional features, as evidenced by the conditional compilation of TLS support. The maintainer actively documents usage patterns through examples covering common scenarios like SPA serving, upload configuration, and HTTPS setup.