Repository navigation
any plan for RFC7616? #2068
Description
Activity
Hello,
I will take this as a feature request, but it can take some time to implement.
Thanks :)
Reacted by jianwuzhaoThank you very much for your reply. I am looking forward to the release of this feature
Hi @hyperxpro ....
If the implementation hasnt started yet, I’d love to take it on and add SHA-256 / SHA-512-256 support per RFC 7616.
Please let me know if that’s okayHi @hyperxpro .... If the implementation hasnt started yet, I’d love to take it on and add SHA-256 / SHA-512-256 support per RFC 7616. Please let me know if that’s okay
You can implement it. We also need test case for this.
okay ...
thank youHave a look at this PR. This still needs some work around test cases.
Reacted by Pratik Katti and jianwuzhaoHi All,
I apologize for the delay on this....I was caught up with some personal work.
i have restarted progress on this and will try to close it as soon as possible.Today i added support for auth-int phase 1.
- Auth-int now works directly for all repeatable request bodies up to 10 MB, including Strings (any charset), byte arrays, Netty ByteBuf, NIO ByteBuffer, ByteArrayBodyGenerator, and FileBodyGenerator.
- Properly calculates digest authentication (RFC-7616 compliant), including correct body hashing in HA2, supporting MD5, SHA-256, SHA-512-256, and their sess variants.
- Properly handles charset negotiation ISO-8859-1 vs UTF-8.
- Graceful, safe error handling.... throws UnsupportedOperationException clearly if the body exceeds 10 MB or is non-repeatable.
- No reader index or buffer position side effects.
- No public API changes....digest response is injected internally via Realm.Builder.
- JUnit 5 tests cover all main scenarios: happy paths, multi-chunk, SHA-256, oversized and unsupported cases, and helper utilities.
for more details please check: #2098
Thanks!
- added a commit that references this issue
on Sep 23, 2025 Hi @hyperxpro
Please let me know if any other changes are needed. once you complete the testing
thanks!
Hello @pratt4
I am very occupied for the time being, so this is being delayed.
I will target this by year's end.Thanks!
- added a commit that references this issue
on Mar 15, 2026 - added a commit that references this issue
on Mar 15, 2026
any plan for RFC7616?
https://github.com/apache/httpcomponents-client/blob/master/httpclient5/src/main/java/org/apache/hc/client5/http/impl/auth/DigestScheme.java