Gno: An interpreted, stack-based Go virtual machine to build succinct and composable apps + Gno.land: a blockchain for timeless code and fair open-source
HTTP basic authentication is a simple authentication mechanism, implemented directly in the protocol. Because it is integrated at a protocol level, web services can be protected by edge web servers like nginx and caddy, without requiring changes in the application itself.
For instance, I could have a simple caddy set up of a gno.land node, password-protecting its RPC, as follows:
However, this is not supported client-side, for instance in gnokey. The URL-spec compliant syntax for providing basic authentication is prefixing the domain with user:password@, as follows:
https://bob:hiccup@rpc.gno.land:443
It would be nice if our clients, like gnokey and gnoclient, supported basic authentication and automatically added the Authorization header in HTTP requests when provided.
HTTP basic authentication is a simple authentication mechanism, implemented directly in the protocol. Because it is integrated at a protocol level, web services can be protected by edge web servers like nginx and caddy, without requiring changes in the application itself.
For instance, I could have a simple caddy set up of a gno.land node, password-protecting its RPC, as follows:
However, this is not supported client-side, for instance in gnokey. The URL-spec compliant syntax for providing basic authentication is prefixing the domain with
user:password@
, as follows:It would be nice if our clients, like
gnokey
andgnoclient
, supported basic authentication and automatically added theAuthorization
header in HTTP requests when provided.