<?xml version="1.0"?>
<feed xmlns="http://www.w3.org/2005/Atom" xml:lang="en">
	<id>https://tech.uvoo.io/index.php?action=history&amp;feed=atom&amp;title=Auth_methods_in_http</id>
	<title>Auth methods in http - Revision history</title>
	<link rel="self" type="application/atom+xml" href="https://tech.uvoo.io/index.php?action=history&amp;feed=atom&amp;title=Auth_methods_in_http"/>
	<link rel="alternate" type="text/html" href="https://tech.uvoo.io/index.php?title=Auth_methods_in_http&amp;action=history"/>
	<updated>2026-04-19T22:01:01Z</updated>
	<subtitle>Revision history for this page on the wiki</subtitle>
	<generator>MediaWiki 1.35.2</generator>
	<entry>
		<id>https://tech.uvoo.io/index.php?title=Auth_methods_in_http&amp;diff=5235&amp;oldid=prev</id>
		<title>Busk: Created page with &quot;``` Basic Authentication: This is the simplest form of HTTP authentication, where the client sends the username and password encoded in Base64 format in the Authorization head...&quot;</title>
		<link rel="alternate" type="text/html" href="https://tech.uvoo.io/index.php?title=Auth_methods_in_http&amp;diff=5235&amp;oldid=prev"/>
		<updated>2024-05-03T21:08:47Z</updated>

		<summary type="html">&lt;p&gt;Created page with &amp;quot;``` Basic Authentication: This is the simplest form of HTTP authentication, where the client sends the username and password encoded in Base64 format in the Authorization head...&amp;quot;&lt;/p&gt;
&lt;p&gt;&lt;b&gt;New page&lt;/b&gt;&lt;/p&gt;&lt;div&gt;```&lt;br /&gt;
Basic Authentication: This is the simplest form of HTTP authentication, where the client sends the username and password encoded in Base64 format in the Authorization header. For example:&lt;br /&gt;
makefile&lt;br /&gt;
Copy code&lt;br /&gt;
Authorization: Basic QWxhZGRpbjpvcGVuIHNlc2FtZQ==&lt;br /&gt;
Bearer Token: This is commonly used in token-based authentication schemes like OAuth 2.0. The client sends a token in the Authorization header prefixed with the word &amp;quot;Bearer&amp;quot;. For example:&lt;br /&gt;
makefile&lt;br /&gt;
Copy code&lt;br /&gt;
Authorization: Bearer eyJhbGciOiJIUzI1NiIsInR5cCI6IkpXVCJ9.eyJzdWIiOiIxMjM0NTY3ODkwIiwibmFtZSI6IkpvaG4gRG9lIiwiaWF0IjoxNTE2MjM5MDIyfQ.SflKxwRJSMeKKF2QT4fwpMeJf36POk6yJV_adQssw5c&lt;br /&gt;
Digest Authentication: This is a more secure form of authentication compared to Basic Authentication. It involves a challenge-response mechanism where the client sends a hash of the username, password, and other request-specific information. For example:&lt;br /&gt;
sql&lt;br /&gt;
Copy code&lt;br /&gt;
Authorization: Digest username=&amp;quot;user&amp;quot;, realm=&amp;quot;example&amp;quot;, nonce=&amp;quot;dcd98b7102dd2f0e8b11d0f600bfb0c093&amp;quot;, uri=&amp;quot;/&amp;quot;, qop=auth, nc=00000001, cnonce=&amp;quot;0a4f113b&amp;quot;, response=&amp;quot;6629fae49393a05397450978507c4ef1&amp;quot;&lt;br /&gt;
AWS Signature Version 4: This is used for authentication in Amazon Web Services (AWS) API requests. It involves signing the request with access key credentials. For example:&lt;br /&gt;
bash&lt;br /&gt;
Copy code&lt;br /&gt;
Authorization: AWS4-HMAC-SHA256 Credential=AKIDEXAMPLE/20210525/us-east-1/s3/aws4_request, SignedHeaders=host;x-amz-content-sha256;x-amz-date, Signature=6d86bb16442e7d53834b7ed6dce825a8e7878cfb31dc9cd30c5b3dc5b858b3d8&lt;br /&gt;
These are just a few examples of authorization mechanisms used in HTTP headers. The choice of mechanism depends on the specific requirements of the application and the security standards being followed.&lt;br /&gt;
```&lt;/div&gt;</summary>
		<author><name>Busk</name></author>
	</entry>
</feed>