[Webkit-unassigned] [Bug 21957] New: WebKit doesn't know how to recover from kCFErrorDomainCFNetwork: 302 very well

[bugzilla-daemon at webkit.org]

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

           Summary: WebKit doesn't know how to recover from
                    kCFErrorDomainCFNetwork: 302 very well
           Product: WebKit
           Version: 528+ (Nightly build)
          Platform: All
        OS/Version: Mac OS X 10.5
            Status: UNCONFIRMED
          Severity: Normal
          Priority: P2
         Component: WebCore Misc.
        AssignedTo: webkit-unassigned at lists.webkit.org
        ReportedBy: matt at re-entry.ca


If I visit a site that breaks the connection such that it generates a error
"kCFErrorDomainCFNetwork: 302", it takes a while, sometimes never, for that
site to start rendering again. A while could be days. The site itself could be
working fine, as I can open the same site in Firefox and curl just fine.

The only workaround I have found is to:

1. Empty Cache
2. Delete the site.webhistory file from
~/Library/Caches/Metadata/Safari/History
3. Remove the site's Cookies in Preferences
4. Restart Safari

It may be that the last step (removing the cookies) is the deciding factor of
the workaround.

I have seen this in Safari 3.1.2, GWT Hosted Mode (uses WebKit + SWT) and the
latest nightly build as of this bug filing.

Searching the web finds many, many people encountering persistent
kCFErrorDomainCFNetwork errors like this, so it appears to be a widespread
problem.

I can generate it pretty easily if I debug GWT in Hosted mode, hit a
breakpoint, then open the page I am debugging in a safari browser instance.

Interestingly, if I stand up Tomcat and replicate the path that GWT uses
(http://localhost:8888/my.module.name/index.html) with a plain HTML file,
Safari still shows the 302 error.


-- 
Configure bugmail: https://bugs.webkit.org/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the assignee for the bug, or are watching the assignee.