[Webkit-unassigned] [Bug 255924] New: URI Fragments Cached After 301 Redirect

[bugzilla-daemon at webkit.org]

https://bugs.webkit.org/show_bug.cgi?id=255924

            Bug ID: 255924
           Summary: URI Fragments Cached After 301 Redirect
           Product: WebKit
           Version: Safari 16
          Hardware: All
                OS: Unspecified
            Status: NEW
          Severity: Major
          Priority: P2
         Component: WebKitGTK
          Assignee: webkit-unassigned at lists.webkit.org
          Reporter: zachshaw1 at gmail.com
                CC: bugs-noreply at webkitgtk.org

Version: Safari 16.4 (macOS & iOS)

When Safari is redirected by a 301 with URI fragments, for example site.com/page#key=123 -> www.site.com/page#key=123, any subsequent page hits after the 301, Safari will use the initial cached URI fragments.

This isn't happening on any other browser, nor is this happening on Safari 16.3 the new URI fragments are correctly picked up.

Disable Caches enabled & private browsing both work fine as well.

-- 
You are receiving this mail because:
You are the assignee for the bug.
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.webkit.org/pipermail/webkit-unassigned/attachments/20230425/57d25cb9/attachment.htm>