liveBook · Manning

HTTP Authorization header

The HTTP Authorization header is a request header that carries credentials or other authentication or authorization information for accessing a resource.

How 2 Manning books explain it

Building Web APIs with ASP.NET Core

The Authorization header is an HTTP request header that carries credentials or authentication information for the requested resource.

How it is used
Attaches bearer tokens to REST API requests and supports authorization checks without server-side sessions.
How deep it goes
Explains bearer-token use and SwaggerUI configuration, but stops short of interceptor implementation and server-side token validation.
Examples
Uses a login-returned JWT, SwaggerUI’s Authorize dialog, and a Program.cs security definition as concrete artifacts.
What you can do after
Operate/configure SwaggerUI to collect a JWT and attach it through the Authorization header on API requests.

Read how Building Web APIs with ASP.NET Core explains HTTP Authorization header →

Spring Security in Action, Second Edition

The HTTP Authorization header carries credentials or authentication tokens in an HTTP request.

How it is used
Authenticates requests to Spring Security-protected REST endpoints through HTTP Basic credentials.
How deep it goes
Explains header construction, Base64 encoding, curl usage, 401 failure, and HTTPS limits, but does not detail token schemes.
Examples
Uses a protected /hello endpoint, curl -u credentials, explicit Authorization construction, and a generated Spring Security password.
What you can do after
Operate a protected Spring endpoint by constructing and testing an HTTP Basic Authorization header with curl.

Read how Spring Security in Action, Second Edition explains HTTP Authorization header →

Related concepts

These guides are generated from the text of Manning books by Manning's knowledge graph and link to the sections they draw on. The full books are available on liveBook and at manning.com.