[SOLVED] [QuteBrowser] URL-redirection works but not in QuteBrowser??
Linux - SoftwareThis forum is for Software issues.
Having a problem installing a new program? Want to know which application is best for the job? Post your question in this forum.
Notices
Welcome to LinuxQuestions.org, a friendly and active Linux Community.
You are currently viewing LQ as a guest. By joining our community you will have the ability to post topics, receive our newsletter, use the advanced search, subscribe to threads and access many other special features. Registration is quick, simple and absolutely free. Join our community today!
Note that registered members see fewer ads, and ContentLink is completely disabled once you log in.
If you have any problems with the registration process or your account login, please contact us. If you need to reset your password, click here.
Having a problem logging in? Please visit this page to clear all LQ-related cookies.
Get a virtual cloud desktop with the Linux distro that you want in less than five minutes with Shells! With over 10 pre-installed distros to choose from, the worry-free installation life is here! Whether you are a digital nomad or just looking for flexibility, Shells can put your Linux machine on the device that you want to use.
Exclusive for LQ members, get up to 45% off per month. Click here for more info.
[QuteBrowser] URL-redirection works but not in QuteBrowser??
Good evening
Preliminary remarks:
1. This is *not* a network-question, as you will see.
2. I have removed .local/share/qutebrowser/webengine prior starting QuteBrowser and then have also executed :reload -f.
The redirection appears to still be valid to about everybody I ask and I can confirm with Firefox or W3M.
In QuteBrowser, however, the URL https://uplawski.eu produces the welcome-page of my hosting association « L'AutreNet ». In their help newsgroup / mailing-list, nobody could reproduce my observations, so far. The admins confirm the active redirection.
For the time I must assume that nothing is wrong with the redirection, but I cannot understand what QuteBrowser does.
This does not make sense, does it?
Last edited by Michael Uplawski; 03-09-2022 at 06:43 AM.
It does make sense depending on the actual config.
Does it actually get redirected to another site, or is it simply an alias in dns for the host name. Does the web server properly return the www name with every request? Is the www site a virual web site or is it the primary site on that host?
What I suspect is that the QuteBrowser is reporting the host address requested and does not switch to the host address replied by the server, possibly caused by not actually switching to a different physical host address.
It does make sense depending on the actual config.
Does it actually get redirected to another site, or is it simply an alias in dns for the host name.
This is an alias, i.e. a redirection that I configured for an ill-designated “subdomain” uplawski.eu, whilst www.uplawski.eu is the locally hosted “subdomain”. I get the impression that the terminology is arbitrary. The domain, which is managed by my registrar – not identical with Web- and Mail-host – is also just “uplawski.eu”. Edit: Wait a moment... I will have to check my configuration in the Registrar's configuration interface. But it should be just like I wrote, above.
OKAY: Let us assume that I do not know anything. This is what I see:
1) Host WWW, type A, 80.67.160.70
The (Web-)Hoster's server IP
I assume that this is the reason, why www.uplawski.eu works alright. FTP and Mail point at the hoster's servers, which is without impact on the issue.
2) Host *, Type A, 46.38.243.234
The registrar's IP
I am afraid this is still a (client-)software issue, as the other browsers cope with the situation.
----- Edit End --------
Quote:
Does the web server properly return the www name with every request?
Tell me how to verify this.
Quote:
Is the www site a virual web site or is it the primary site on that host?
Primary.
Quote:
What I suspect is that the QuteBrowser is reporting the host address requested and does not switch to the host address replied by the server, possibly caused by not actually switching to a different physical host address.
If there is a configuration option to set, I guess I'll have to register with github again... or drop QuteBrowser quite simply.
Last edited by Michael Uplawski; 03-09-2022 at 07:01 AM.
All this speculation can be avoided/answered by getting QuteBrowser to display/log HTTP requests and responses, then comparing the request that has the issue to the one that doesn't.
The log files usually are at /var/log/httpd/ on the server which usually shows all communications.
How to get the browser to log its info is another story.
I have removed the current config.py for QuteBrowser but see no change. In view of the many alternatives, I tend to just give up on QuteBrowser or – at least – to not care any more. Anyway, my comprehension of your hints diminishes with each contribution.
Which distro are you using it on? Which version of qutebrowser?
Debian Bookworm
qutebrowser v2.4.0
Backend: QtWebEngine 5.15.8, based on Chromium 87.0.4280.144
Qt: 5.15.2
Quote:
Have you also tried removing the complete ~/.config/qutebrowser directory?
I did (prior starting qutebrowser) and nothing changed, same behavior with https://uplawski.eu which leads to the startpage of l'AutreNet (www.lautre.net).
Backend: QtWebEngine 5.15.8, based on Chromium 87.0.4280.144
So does it have F12 developer tools or not?
If so, press F12, goto the network tab, ensure both "Preserve log" and "Disable cache" options are ticked, ensure "All" is selected, clear any existing rows, then visit https://uplawski.eu/ and look at what comes back.
Post the raw HTTP request and response (i.e. use "view source" option in Chromium) for the first response.
F12 did not do anything, :devtools changed the cursor into a gray dot (however) but scrolling was impossible. Then I noticed a small strange border on the right of the browser. Okay, I did what you told me.
Since pen https://uplawski.eu the sought page is displayed immediately. All expected ressources are delivered, html, scripts and images, from www.uplawski.eu. F12 still does nothing but toggling the devtools closes the window. After that and in the same tab, I can navigate from and to https://uplawski.eu, without observing any strange behavior.
In any new tab, however, the “old” phenomenon returns, where instead of my start-page, that of www.lautre.net appears.
Edit some hours later: boughtonp, you have solved the problem. Call :devtools, check checkboxes, visit URL. Ω
Last edited by Michael Uplawski; 03-11-2022 at 06:01 AM.
It must have been. All: Allow me to ignore forever, which cache was concerned, as I do not have the brain to think of yet another one.
Apart from that, the domains and those “sub-domains” concerned exist since I joined L'AutreNet. There were server errors which had been corrected, but *never* had there been a reason to identify their start-page with mine. Recently, there had been none such event. Let us say, this was a caching issue. Then it is nice to have been pointed at it, but to get stuff out of ... – I had emptied/deleted the QuteBrowser-cache, but anyway – ... out of the cache (whichever), you have to store it there, first.
It would not be polite to write that I do not want to know. And stuff is piling up, there. Thank you for wasting your time with me.
The biggest achievement of this thread is that I won the courage to draw that border-line into the window to finally take a look at the devtools widget.
Last edited by Michael Uplawski; 03-11-2022 at 11:20 PM.
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.