[Webkit-unassigned] [Bug 25263] New: WebKit GTK with libsoup won't recognize proxies
bugzilla-daemon at webkit.org
bugzilla-daemon at webkit.org
Fri Apr 17 02:07:48 PDT 2009
https://bugs.webkit.org/show_bug.cgi?id=25263
Summary: WebKit GTK with libsoup won't recognize proxies
Product: WebKit
Version: 528+ (Nightly build)
Platform: PC
OS/Version: Linux
Status: UNCONFIRMED
Severity: Normal
Priority: P2
Component: WebKit Gtk
AssignedTo: webkit-unassigned at lists.webkit.org
ReportedBy: coolwanglu at gmail.com
Environment:
Debian 2.6.18 amd64
latest libsoup & libproxy till now
WebKit 1.1.5 (should also affect latest nightly build)
My computer connect with Internet through a HTTP proxy, which is set in the
'http_proxy' environment variable.
I've been working on WebKit for months, at first, while I was using 1.0.1,
(with curl as its backend), everything's all right. But recently I updated it
to 1.1.5, and found that GtkLauncher could not load http://www.google.com.
It took me some time to realize that the network backend has been changed to
libsoup. And I did test my libsoup, which worked well.
It took me another some time to compare
WebCore/platform/network/soup/ResourceHandlSoup.cpp and test.c in libsoup
tests. And at last my conclusion is maybe the proxy-resolver feature is not
enabled. So I made a dirty patch:
1.in configure, add dependency rule of libsoup-gnome-2.4 (I failed in editing
configure.ac and re-automake, for some unknown reason)
2.in WebCore/platform/network/soup/ResourceHandleSoup.cpp
1) at the beginning, add
#include <libsoup/soup-gnome.h>
2) at arount line 444, replace the body of function 'static SoupSession*
createSoupSession()' with the following code
return
soup_session_async_new_with_options(SOUP_SESSION_ADD_FEATURE_BY_TYPE,
SOUP_TYPE_GNOME_FEATURES_2_26, NULL);
I don't know whether it'll affect other parts of webkitgtk, but at least it
works for me
so please check this, thx
--
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.
More information about the webkit-unassigned
mailing list