claimchain http block server
Simple http-server for “claimchain” blocks. It uses Flask to serve HTTP GET and authenticated PUT requests.
getting started
install with pip install cchttpserver
run python -m cchttpserver which will tell you to create a config file and provides a simple example. Create a config.py file and run CCHTTPSERVER_CONFIG=config.py python -m cchttpserver.
Then open another terminal and open a python prompt with “python” and type something like:
import requests requests.put("http://USER:PASSWORD@localhost:5000/key1", "data1") r = requests.get("http://localhost:5000/key1") assert r.status_code == 200 requests.delete("http://USER:PASSWORD@localhost:5000/USER/") r = requests.get("http://localhost:5000/key1") assert r.status_code == 404
Release files for cchttpserver 0.6.3
For a detailed explanation of source distributions (sdists) and built distributions (wheels), please see the package formats documentation.
Source distribution (sdist)
| File | Size | Uploaded | Provenance | |
|---|---|---|---|---|
| cchttpserver-0.6.3.tar.gz | 5.5 kB | Without provenance | Details |
Release files / cchttpserver-0.6.3.tar.gz
| Download URL | cchttpserver-0.6.3.tar.gz |
|---|---|
| Size | 5.5 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
75ad0f8fb406025892ee4945c88df9cdb0d4976c4449813a31964433b385df4f
|
|
BLAKE2b-256 checksum How to use checksums |
df82be1151013573004e2f4d126735c19bb213049695684af00f26fe61f8f81d
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
twine/1.12.1 pkginfo/1.4.2 requests/2.20.1 setuptools/40.6.2 requests-toolbelt/0.8.0 tqdm/4.28.1 CPython/2.7.15rc1
|
Security for cchttpserver 0.6.3
Provenance
Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.
No provenance found
None of the files in this release were uploaded with provenance metadata.
A note on package security
PyPI is a repository for distributing packages, not a service for auditing them. While third-party security researchers and our staff do their best to detect and remove malicious packages, PyPI cannot guarantee the quality, security or suitability of any given package.
