https://bugs.kde.org/show_bug.cgi?id=398175
--- Comment #2 from Tobias Leupold <tobias.leup...@gmx.de> ---
So, it's one year and I'm still facing the same problem ;-)
Aüpparently, Falkon doesn't follow the redirect ("Location" header) announced
by the router before the login. This is what "LC_ALL=C wget --server-response
google.de" outputs:
tobias@think ~ $ LC_ALL=C wget --server-response google.de
--2020-08-16 19:26:30-- http://google.de/
Resolving google.de... 172.217.23.35, 2a00:1450:4016:804::2003
Connecting to google.de|172.217.23.35|:80... connected.
HTTP request sent, awaiting response...
HTTP/1.1 302 Hotspot login required
Cache-Control: no-cache
Content-Length: 135
Content-Type: text/html
Date: Sun, 16 Aug 2020 10:53:15 GMT
Expires: 0
Location: http://172.18.0.133/login?dst=http%3A%2F%2Fgoogle.de%2F
Location: http://172.18.0.133/login?dst=http%3A%2F%2Fgoogle.de%2F
[following]
--2020-08-16 19:26:30--
http://172.18.0.133/login?dst=http%3A%2F%2Fgoogle.de%2F
Connecting to 172.18.0.133:80... connected.
HTTP request sent, awaiting response...
HTTP/1.1 200 OK
Cache-Control: no-cache
Connection: Keep-Alive
Content-Length: 4540
Content-Type: text/html
Date: Sun, 16 Aug 2020 10:53:15 GMT
Expires: 0
Length: 4540 (4.4K) [text/html]
Saving to: 'index.html'
It answers with "HTTP/1.1 302 Hotspot login required", followed by the
hotspot's login page "Location: http://172.18.0.133/login";.
Shouldn't Falkon follow this redirect? Like wget, Firefox and Chrome do?
--
You are receiving this mail because:
You are watching all bug changes.
