Skip to content

any plan for RFC7616? #2068

Activity

  1. added theissue type on Apr 7, 2025
  2. hyperxpro commented on Apr 7, 2025

    @hyperxpro
    Member

    Hello,

    I will take this as a feature request, but it can take some time to implement.

    Thanks :)

  3. jianwuzhao commented on Apr 8, 2025

    @jianwuzhao
    Author

    Thank you very much for your reply. I am looking forward to the release of this feature

  4. pratt4 commented on May 10, 2025

    @pratt4
    Contributor

    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 okay

  5. hyperxpro commented on May 10, 2025

    @hyperxpro
    Member

    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 okay

    You can implement it. We also need test case for this.

  6. pratt4 commented on May 10, 2025

    @pratt4
    Contributor

    okay ...
    thank you

  7. hyperxpro commented on May 10, 2025

    @hyperxpro
    Member

    #2089

    Have a look at this PR. This still needs some work around test cases.

  8. pratt4 commented on Jul 20, 2025

    @pratt4
    Contributor

    Hi 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!

  9. added a commit that references this issue on Sep 23, 2025
    a5763a6
  10. pratt4 commented on Oct 27, 2025

    @pratt4
    Contributor

    Hi @hyperxpro

    Please let me know if any other changes are needed. once you complete the testing

    thanks!

  11. hyperxpro commented on Oct 27, 2025

    @hyperxpro
    Member

    Hello @pratt4

    I am very occupied for the time being, so this is being delayed.
    I will target this by year's end.

    Thanks!

  12. added a commit that references this issue on Mar 15, 2026
    05c437e
  13. added a commit that references this issue on Mar 15, 2026
    4168dd1
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Projects

    No projects

      Milestone

      No milestone

      Relationships

      None yet

      Development

      No branches or pull requests

      Issue actions