I am missing the compatibility picture here. How will this affect existing web pages, and what happens to browsers that do not support this is we add support?

/Daniel

On 2023-06-20 18:13, Deomid "rojer" Ryabkov wrote:


        Contact emails

roj...@gmail.com


        Explainer

None


        Specification

https://datatracker.ietf.org/doc/html/rfc7616


        Summary

https://datatracker.ietf.org/doc/html/rfc7616 specifies SHA-256 and SHA-512-256 algorithms for the HTTP digest authentication scheme, in addition to the obsolete and insecure MD5. It also specifies way of concealing the username, provided that server supports it. Firefox supports algorithm=SHA-256 since 93, but not SHA-512-256 or username hashing. https://chromium-review.googlesource.com/c/chromium/src/+/4611879 is the pending CL.



        Blink component

Blink>Network <https://bugs.chromium.org/p/chromium/issues/list?q=component:Blink%3ENetwork>


        TAG review

None


        TAG review status

Not applicable


        Risks



        Interoperability and Compatibility



/Gecko/: Shipped/Shipping (https://bugzilla.mozilla.org/show_bug.cgi?id=472823)

/WebKit/: No signal

/Web developers/: No signals

/Other signals/:


        WebView application risks

Does this intent deprecate or change behavior of existing APIs, such that it has potentially high risk for Android WebView-based applications?



        Debuggability



        Will this feature be supported on all six Blink platforms
        (Windows, Mac, Linux, Chrome OS, Android, and Android WebView)?

Yes


        Is this feature fully tested by web-platform-tests
        
<https://chromium.googlesource.com/chromium/src/+/main/docs/testing/web_platform_tests.md>?

No


        Flag name



        Requires code in //chrome?

False


        Tracking bug

https://bugs.chromium.org/p/chromium/issues/detail?id=1160478


        Estimated milestones

Shipping on desktop     116

Shipping on Android     116



        Anticipated spec changes

Open questions about a feature may be a source of future web compat or interop issues. Please list open issues (e.g. links to known github issues in the project for the feature specification) whose resolution may introduce web compat/interop risk (e.g., changing to naming or structure of the API in a non-backward-compatible way).



        Link to entry on the Chrome Platform Status

https://chromestatus.com/feature/5139896267702272


        Links to previous Intent discussions



This intent message was generated by Chrome Platform Status <https://chromestatus.com/>.

--
Deomid "rojer" Ryabkov
ro...@rojer.me
--
You received this message because you are subscribed to the Google Groups "blink-dev" group. To unsubscribe from this group and stop receiving emails from it, send an email to blink-dev+unsubscr...@chromium.org. To view this discussion on the web visit https://groups.google.com/a/chromium.org/d/msgid/blink-dev/CABFmFwr1XJbEU-yWbe2Whx%2Bago2njJFg-gOOdKzEj0%3DGVzP%3D0g%40mail.gmail.com <https://groups.google.com/a/chromium.org/d/msgid/blink-dev/CABFmFwr1XJbEU-yWbe2Whx%2Bago2njJFg-gOOdKzEj0%3DGVzP%3D0g%40mail.gmail.com?utm_medium=email&utm_source=footer>.

--
You received this message because you are subscribed to the Google Groups 
"blink-dev" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to blink-dev+unsubscr...@chromium.org.
To view this discussion on the web visit 
https://groups.google.com/a/chromium.org/d/msgid/blink-dev/938a943a-1c20-8bf0-de73-11bc6c9a0467%40gmail.com.

Reply via email to