Skip to content

Explicitly mention .headers() functions in README docs, near the PR r… #107

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
lulf merged 3 commits into from
May 23, 2025
Merged

Explicitly mention .headers() functions in README docs, near the PR r… #107

Changes from all commits
Commits
Show all changes
3 commits
Select commit Hold shift + click to select a range
5538a22
Explicitly mention .headers() functions in README docs, near the PR r…
swork Jan 31, 2025
ba607da
Merge branch 'main' into swork-doc-headers-corrected
swork Feb 7, 2025
60a022a
Merge branch 'main' into swork-doc-headers-corrected
rmja Mar 28, 2025
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
2 changes: 2 additions & 0 deletions README.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -34,6 +34,8 @@ The client is still lacking many features, but can perform basic HTTP GET/PUT/PO

NOTE: TLS verification is not supported in no_std environments for `embedded-tls`.

In addition to common headers like `.content_type()` on requests, broader `.headers()` functions on both request and response objects access arbitrary header values.

If you are missing a feature or would like an improvement, please raise an issue or a PR.

## TLS 1.2*, 1.3 and Supported Cipher Suites
Expand Down