[Webkit-unassigned] [Bug 14651] New: [CURL] didReceiveResponse() only called for HTTP loads

bugzilla-daemon at webkit.org bugzilla-daemon at webkit.org
Tue Jul 17 19:10:50 PDT 2007


           Summary: [CURL] didReceiveResponse() only called for HTTP loads
           Product: WebKit
           Version: 522+ (nightly)
          Platform: All
        OS/Version: All
            Status: UNCONFIRMED
          Severity: Normal
          Priority: P2
         Component: WebCore Misc.
        AssignedTo: webkit-unassigned at lists.webkit.org
        ReportedBy: kevino at theolliviers.com

The current implementation of the CURL loader calls didReceiveResponse only
when receiving HTTP headers. This doesn't handle URLs using other protocols,
such as file://. This causes problems with loading css files from disk because
WebCore/loader/CachedCSSStyleSheet.cpp depends on m_response being set to
determine the absolute URL of the css file.

I don't have a patch yet, as I'm not quite sure where the best place to fire
didReceiveResponse would be for other protocols. Ideally, it would be from the
first successful curl_multi_perform call for each handle, but I'm not sure if
there's currently a way to track that.

Anyone more familiar with the CURL loader have any suggestions on how best to
implement this?

Configure bugmail: http://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.

More information about the webkit-unassigned mailing list