Re: Trouble with konqueror on http authentication

On sabato 30 gennaio 2021 09:25:45 CET Erik Rull wrote:
> Stefano Crocco wrote:
> > On gioved=EC 28 gennaio 2021 23:39:00 CET Erik Rull wrote:
> >> Stefano Crocco wrote:
> >>> On marted=EC 26 gennaio 2021 22:04:15 CET Erik Rull wrote:
> >>>> Hi all,
> >>>>=20
> >>>> I don't know how to get this working again. I just updated to 20.04
> >>>> from
> >>>> 16.04 (kubuntu LTS) and before the update this was working great:
> >>>>=20
> >>>> I start my Linux box (just power on) and remote SSH into the system
> >>>> (X-Forwarding enabled). Then I open my applications and also konquer=
or.
> >>>> This works all fine and smoothly, websites are displayed fine. Until=
 I
> >>>> try to access a website with HTTP-Authentication - there I directly =
get
> >>>> a 401 - no asking for a password, nothing, just the 401 page directl=
y.
> >>>> Firefox prompts me for the username/password and shows me the page
> >>>> behind the
> >>>> authentication. So the server is fine. I tried multiple servers and
> >>>> konqueror behaves always the same.
> >>>>=20
> >>>> Any idea what I broke during the update?
> >>>>=20
> >>>> Best regards,
> >>>>=20
> >>>> Erik
> >>>=20
> >>> Hello Erik,
> >>> do you by any chance know whether your previous version of Konqueror
> >>> still
> >>> used the WebKit engine or had it already switched to QtWebEngine? In =
the
> >>> first case, I think you can have found yet another feature which stop=
ped
> >>> working with the switch to the new engine.
> >>>=20
> >>> If your current Kubuntu version still provides KWebKitPart, you could
> >>> also
> >>> try installing it, select it as default web engine in the General tab=
 of
> >>> the Konqueror settings page and check whether the HTTP Authentication
> >>> works with it. If it does, the problem lies with QtWebEngine, otherwi=
se,
> >>> we'll need to investigate somewhere else.
> >>>=20
> >>> Stefano
> >>=20
> >> Hi Stefano,
> >>=20
> >> I don't know exactly. How can I check this and / or switch the engine?
> >> When opening konqueror and access e.g. google.com then a new process is
> >> listed with QtWebEngineProcess - so I assume this is the QtWebEngine.
> >> I tried to search for kwebkit in aptitude - nothing found...
> >> Maybe it is hidden in a different named package?
> >>=20
> >> Best regards,
> >>=20
> >> Erik
> >=20
> > Hello Erik,
> > the current version of Konqueror uses QtWebEngine by default. I fear th=
at
> > kwebkitpart may have been removed from it (for instance, I know it's be=
en
> > removed from Gentoo). In the weekend, I'll try to install an Ubuntu
> > virtual
> > machine with both Ubuntu 20.04 and 16.04 to check what the situation is.
> >=20
> > Stefano
>=20
> Hi Stefano,
>=20
>=20
> Thanks a lot!
> Please try the SSH access before you logged in.
>=20
> I found out something new meanwhile:
> When NOT logging in directly on the desktop - I get the 401 with konqueror
> directly via SSH - that I described already.
> BUT - When logging into the system directly (local screen and keyboard) a=
nd
> THEN open the konqueror remotely via SSH, konqueror does NOT display the
> 401 - it "waits". But what happens in parallel on the local screen: the
> authentication dialog of the requested website pops up!
>=20
> So "something" is different when being logged in directly. But the behavi=
or
> is still odd, because you have no chance to access the login dialog via
> SSH...
>=20
> Any ideas?
>=20
> Best regards,
>=20
> Erik

Hello Erik,
I can confirm that, unfortunately, KUbuntu 20.4 doesn't include KWebKitPart=
=2E If=20
you are comfortable building programs from source, you can download it from=
=20
https://invent.kde.org/libraries/kwebkitpart and install it (it requires=20
kdewebkit which is available in KUbuntu). After installing it, in the Gener=
al=20
tab of Konqueror settings dialog, you'll be able to set KWebKit as default =
web=20
browser engine. I'm not sure whether this will fix your issue or not, howev=
er.

As I've never used ssh with X-forwarding, could you please explain step by=
=20
step what you did to in the two situations you described? I tried setting u=
p a=20
very minimalistic server with http authentication and accessing it with usi=
ng=20
Konqueror from ssh and I had no problems neither with the old KWebKit nor w=
ith=20
the new QtWebEngine.

Stefano