On Wed, Jan 27, 2021 at 07:18:29PM PST, A Dog wrote:
> It appears that otter-browser, when using QtWebEngine as its backend, is
> unable to use proxies. I've tried the following:
>
> 1) a proxy defined in the browser settings, selected:
> a) in the settings interface itself,
> b) through the Quick Preferences menu;
> 2) the environment variables http{,s}_proxy and uppercase equivalents.
>
> None of these appear to do anything. The computer I'm running it on is
> blocked from accessing the global Internet except through a proxy, and
> thus the result is a failure to load any non-local web pages whatsoever,
> which effectively renders the browser unusable on that host.
>
> This may have security and/or privacy implications for anyone wishing to
> use different proxies for different websites without blocking non-LAN
> access per se, as your "real IP" will silently be used to connect
> instead with no indication to the user that their proxy settings are
> being ignored.
>
> This is not a regression introduced in the latest version of the browser
> itself, as changing the port Makefile to use QtWebKit instead fixes the
> issue. I am currently doing this as a workaround.
>
> Steps to replicate:
>
> 1) Setup a local HTTP proxy;
> 2) Block a host (other than the proxy host) from everything but the LAN;
> 3) On that host, attempt any method of setting a proxy in otter-browser;
> 4) Load any non-local web page. It will fail to connect.
Am I the only one this is happening to? Can anyone confirm they were
able to use an HTTP proxy with the new otter-browser (and that their
traffic is actually being proxied?) Anything I might be doing wrong on
my end / tips for troubleshooting this?
Currently I am only able to make use of otter by building it locally
with the attached patch, but this is unsustainable in the long run.
--
A Dog
DIFF *NOT* PROPOSED FOR INCLUSION IN THE PORTS TREE!
This is just to show what I had to do to get www/otter-browser to work
with http proxies. See original post for steps to replicate and the
various proxy configuration methods I've tried under QTWebEngine.
A. Dog
diff --git a/www/otter-browser/Makefile b/www/otter-browser/Makefile
index 9d475f6e460..ca985bc5eda 100644
--- a/www/otter-browser/Makefile
+++ b/www/otter-browser/Makefile
@@ -17,8 +17,8 @@ EXTRACT_SUFX = .tar.bz2
PERMIT_PACKAGE = Yes
WANTLIB += ${COMPILER_LIBCXX} Qt5Core Qt5DBus Qt5Gui Qt5Multimedia
-WANTLIB += Qt5Network Qt5Positioning Qt5PrintSupport Qt5Qml Qt5QmlModels
-WANTLIB += Qt5Quick Qt5Svg Qt5WebChannel Qt5WebEngineCore Qt5WebEngineWidgets
+WANTLIB += Qt5Network Qt5Positioning Qt5PrintSupport #Qt5Qml Qt5QmlModels
+WANTLIB += Qt5Quick Qt5Svg Qt5WebChannel Qt5WebKit Qt5WebKitWidgets
WANTLIB += Qt5Widgets Qt5XmlPatterns c hunspell-1.7 m
MODULES = devel/cmake x11/qt5
@@ -29,11 +29,11 @@ LIB_DEPENDS = textproc/hunspell \
x11/qt5/qtdeclarative \
x11/qt5/qtmultimedia \
x11/qt5/qtsvg \
- x11/qt5/qtwebengine \
+ x11/qt5/qtwebkit>=5.212.0 \
x11/qt5/qtxmlpatterns
-CONFIGURE_ARGS += -DENABLE_QTWEBENGINE=ON \
- -DENABLE_QTWEBKIT=OFF
+CONFIGURE_ARGS += -DENABLE_QTWEBENGINE=OFF \
+ -DENABLE_QTWEBKIT=ON
NO_TEST = Yes
