liveBook · Manning

Base64

As explained in Logs and Telemetry

Base64 encoding represents binary or textual data as ASCII characters using a 64-character alphabet.

Base64 represents binary or textual data with ASCII characters from a 64-character alphabet. In HTTP Basic authentication, the authorization header carries a random-looking Base64 value formed from a username and password separated by a colon. section 5.8

Inspecting Basic authentication

A Fluent Bit HTTP output sends credentials to WireMock. The authorization value can be verified with base64encode.org, but transmitting credentials without HTTPS exposes them in cleartext; use certificates when security matters. section 5.8

How Logs and Telemetry covers it

How deep it goes
Shows the credential representation and verification step, but does not explain the encoding algorithm or decoding process.
Examples
Uses a username and password joined by a colon, displayed as a Basic authorization value in WireMock console output.
What you can do after
Evaluate an authorization value with base64encode.org and recognize why HTTPS matters when transmitting credentials.
How it connects
Connects Base64 with HTTP Basic authentication, authorization headers, credentials, HTTPS, WireMock, and Fluent Bit.

Also explained in

Compare how 7 books explain Base64 →

Related concepts

This explainer was generated by Manning's knowledge graph from the text of Logs and Telemetry. The section links point to the parts of the book it draws on.