GitHub - sterchelen/hssp: CLI to avoid remembering the http status codes
source link: https://github.com/sterchelen/hssp
Go to the source link to view the article. You can view the picture content, updated content and better typesetting reading experience. If the link is broken, please click the button below to view the snapshot at that time.
hssp for Http StatuS where the two capitals S replace the two ts of http
.
This CLI is here to help you find/remember the meaning of an http status code.
Historically speaking, this tool was written after struggling with my memory to find the meaning of a code. Some tools already exist but installing Node.js is too much for me...
Installation
From source
To install hssp, first you need to install the dependencies:
- Arch Linux
pacman -S go make
Then, run:
make build
make install
Quick start
$ hssp code --help
This command displays the description for the given http code
with its corresponding class and its RFC.
Usage:
hssp code CODE [...] [flags]
Flags:
-h, --help help for code
Meaning of 204
$ hssp code 204
+------+------------+-------------+---------+
| CODE | CLASS | DESCRIPTION | RFC |
+------+------------+-------------+---------+
| 204 | Successful | No Content | RFC7231 |
+------+------------+-------------+---------+
Class
$ hssp class --help
This command displays the list of http status codes corresponding
to the given class, which may be specified as a number (1-5),
a class category string (1xx, 2xx, 3xx, 4xx, 5xx),
or the class name, i.e. informational, successful, redirect, clienterror,
or servererror
Usage:
hssp class [CLASS | NAME] [...] [flags]
Flags:
-h, --help help for class
List of status codes for the Successful class
$ hssp class 2
+------+------------+-------------------------------+---------+
| CODE | CLASS | DESCRIPTION | RFC |
+------+------------+-------------------------------+---------+
| 200 | Successful | OK | RFC7231 |
| 201 | Successful | Created | RFC7231 |
| 202 | Successful | Accepted | RFC7231 |
| 203 | Successful | Non-Authoritative Information | RFC7231 |
| 204 | Successful | No Content | RFC7231 |
| 205 | Successful | Reset Content | RFC7231 |
| 206 | Successful | Partial Content | RFC7231 |
| 207 | Successful | Multi-Status | RFC4918 |
| 208 | Successful | Already Reported | RFC5842 |
| 226 | Successful | IM Used | RFC3229 |
+------+------------+-------------------------------+---------+
Contribution
No other words than "Welcome guys" :)
Recommend
-
38
Rust 1.26 introduced the ability to return a Result from the main method, which was a great ergonomics improvement especially for small CLI applications. If your application returns an...
-
9
Web Development...
-
4
A Non-Jargon Guide to HTTP Status CodesMichelle OfiweMar 22, 202110 min readHTTP, or HyperText Transfer Protocol, is the backbone of the Wo...
-
8
Are there standard output status codes in Linux? advertisements A process is considered to have completed correctly in Linux if its exit statu...
-
5
About this Episode Catalin Ciubotaru joins the adventure to discuss how to get Angular Universal to send server side HTTP codes to the browser from the back-end when Angular is geared toward the front-end and does...
-
1
The list of HTTP status codes and their explanation Author: Hamster, ...
-
4
-
6
Everything You Need to Know About HTTP Response Status CodesHTTP response codes are often ignored, but they are a really important mechanism to standardize responses from remote servers. When a program (or user) issues a r...
-
5
10 Error Status Codes When Building APIs for the First Time and How To Fix Them ...
-
4
You're Not Using HTTP Status Codes Right HTTP status codes are like short messages returned from a server whenever we request or interact with a resource on the serve...
About Joyk
Aggregate valuable and interesting links.
Joyk means Joy of geeK