https://github.com/serialt/httpstat
https://github.com/serialt/httpstat
Last synced: 27 days ago
JSON representation
- Host: GitHub
- URL: https://github.com/serialt/httpstat
- Owner: serialt
- License: mit
- Created: 2023-09-20T07:24:00.000Z (over 2 years ago)
- Default Branch: main
- Last Pushed: 2023-09-20T07:29:22.000Z (over 2 years ago)
- Last Synced: 2025-12-27T02:20:51.556Z (6 months ago)
- Language: Go
- Size: 10.2 MB
- Stars: 0
- Watchers: 1
- Forks: 0
- Open Issues: 0
-
Metadata Files:
- Readme: README.md
- License: LICENSE
Awesome Lists containing this project
README
# httpstat [](https://github.com/davecheney/httpstat/actions/workflows/push.yml) [](https://goreportcard.com/report/github.com/davecheney/httpstat)

Imitation is the sincerest form of flattery.
But seriously, https://github.com/reorx/httpstat is the new hotness, and this is a shameless rip off.
## Installation
`httpstat` requires Go 1.20 or later.
```
$ go install github.com/serialt/httpstat@latest
```
## Usage
```
$ httpstat https://example.com/
```
## Features
- Windows/BSD/Linux supported.
- HTTP and HTTPS are supported, for self signed certificates use `-k`.
- Skip timing the body of a response with `-I`.
- Follow 30x redirects with `-L`.
- Change HTTP method with `-X METHOD`.
- Provide a `PUT` or `POST` request body with `-d string`. To supply the `PUT` or `POST` body as a file, use `-d @filename`.
- Add extra request headers with `-H 'Name: value'`.
- The response body is usually discarded, you can use `-o filename` to save it to a file, or `-O` to save it to the file name suggested by the server.
- HTTP/HTTPS proxies supported via the usual `HTTP_PROXY`/`HTTPS_PROXY` env vars (as well as lower case variants).
- Supply your own client side certificate with `-E cert.pem`.
## Contributing
Bug reports are most welcome, but with the exception of #5, this project is closed.
Pull requests must include a `fixes #NNN` or `updates #NNN` comment.
Please discuss your design on the accompanying issue before submitting a pull request. If there is no suitable issue, please open one to discuss the feature before slinging code. Thank you.