HTTP encodings, headers, media types, methods, relations and status codes, all summarized and linking to their specification.
HTTP status codes as haiku.
The active_workflow_agent library helps you to write your own ActiveWorkflow agents in Ruby using ActiveWorkflow's remote agent API. “Remote” in this context means that agents run in separate processes from ActiveWorkflow itself. Communication between agents and ActiveWorkflow takes place via HTTP. Each agent is effectively an HTTP server which ActiveWorkflow connects to and interacts with via the remote agent API protocol.
Github: https://github.com/automaticmode/active_workflow_agent
The activeworkflow_agent library helps you to write your own ActiveWorkflow agents in Python using ActiveWorkflow's remote agent API. “Remote” in this context means that agents run in separate processes from ActiveWorkflow itself. Communication between agents and ActiveWorkflow takes place via HTTP. Each agent is effectively an HTTP service or microservice which ActiveWorkflow connects to and interacts with as long as it supports the remote agent API protocol.
Github: https://github.com/automaticmode/activeworkflow-agent-python
You can create your own agents by developing simple services that implement ActiveWorkflow's Remote Agent API. “Remote” in this context means that agents run in separate processes from ActiveWorkflow itself. Communication between agents and ActiveWorkflow takes place via HTTP. Each agent is effectively an HTTP service or microservice which ActiveWorkflow interacts with via an RPC protocol.
https://github.com/automaticmode/active_workflow/blob/master/lib/remote_agents.rb
https://github.com/automaticmode/active_workflow/blob/master/spec/features/use_remote_agent.rb
https://github.com/automaticmode/active_workflow/blob/master/spec/lib/remote_agents_spec.rb
A site that has different gardening-related pictures depicting each HTTP response code.
Tool that tests MANY url bypasses to reach a 40X protected page. If you wonder why this code is nothing but a dirty curl wrapper, here's why:
- Most of the python requests do url/path/parameter encoding/decoding, and I hate this.
- If I submit raw chars, I want raw chars to be sent.
- If I send a weird path, I want it weird, not normalized.
This is surprisingly hard to achieve in python without loosing all of the lib goodies like parsing, ssl/tls encapsulation and so on. So, be like me, use curl as a backend, it's gonna be just fine.
A very simple webhook server to launch shell scripts.
Dogs for every HyperText Transfer Protocol response status code.
![https://http.dog/[code].jpg](https://http.dog/[code].jpg){kind=link}
Resty provides a simple, concise shell interface for interacting with REST services. Since it is implemented as functions in your shell and not in its own separate command environment you have access to all the usual shell tools. Cookies are supported automatically and stored in a file locally. Most of the arguments are remembered from one call to the next to save typing. It has pretty good defaults for most purposes. Additionally, resty allows you to easily provide your own options to be passed directly to curl, so even the most complex requests can be accomplished with the minimum amount of command line pain.
Implemented as a shell script that you source: . /path/to/resty
Basically, Resty lets you treat HTTP requests to a REST API like a series of CLI commands.
WaveDB is SQLite with a HTTP interface.
It is a ~6MB (~2MB UPX-compressed) self-contained, zero-dependency executable that bundles SQLite 3.35.5 (2021-04-19) with JSON1, RTREE, FTS5, GEOPOLY, STAT4, and SOUNDEX.
If you are already a fan of SQLite, WaveDB acts as a thin HTTP-server wrapper that lets you access your SQLite databases over a network.
WaveDB can be used as a lightweight, cross-platform, installation-free companion SQL database for Wave apps. The h2o-wave package includes non-blocking async functions to access WaveDB.
Database files managed by WaveDB are 100% interoperable with SQLite, which means you can manage them with the sqlite3 CLI, backup/restore/transfer them as usual, or use Litestream for replication.
webhook is a lightweight configurable tool written in Go, that allows you to easily create HTTP endpoints (hooks) on your server, which you can use to execute configured commands. You can also pass data from the HTTP request (such as headers, payload or query variables) to your commands. webhook also allows you to specify rules which have to be satisfied in order for the hook to be triggered.
A fairly simple webhook service that listens to a signald socket and exposes messages via HTTP. Uses YAML for its config files. Can also send messages (replies?) using one or more template files as a basis.
teler is an real-time intrusion detection and threat alert based on web log that runs in a terminal with resources that we collect and provide by the community. Requires minimal configuration. Run your web server logs through it and see what it comes up with.
This module allows sending XMPP <message> stanzas via a simple HTTP API. It's currently in the extra modules Mercurial repository.
curl http://example.com:5280/msg/user -u
me@example.com:mypassword -H "Content-Type: text/plain"
-d "Server@host has just crashed!"
A utility which turns any shell command into a REST API.
A cut down version of Requests for MicroPython. Rejoice!
A free, fast and beautiful API request builder (web alternative to Postman) used by 60k+ developers. Play around with requests when developing against an API. Supports all HTTP verbs. Is technically a PWA.
Online demo (in devtools): https://postwoman.io
Updog is a replacement for Python's SimpleHTTPServer. It allows uploading and downloading via HTTP/S, can set ad hoc SSL certificates and use http basic auth.