[ RESOLVED ]
It was the User Agent
string in my #Qutebrowser config.py
that was causing issues only with #DuckDuckGo search results.
Is it just me or this happening elsewhere on #DuckDuckGo ?
If I go to start.duckduckgo.com and then enter a search say #FreeBSD . If I then click on a result any of them I get the Nginx screen with 400 Bad Request.
Google works fine and other sites it's just #DDG
This entry was edited (1 month ago)
reshared this
Stefano Marinelli
in reply to Justine Smithies • • •Justine Smithies
in reply to Justine Smithies • • •Paul Wilde
in reply to Justine Smithies • • •Perhaps DDG is giving you dodgy links - does it work better in Private mode (i.e. cleared cache) or on a different web browser?
Justine Smithies
in reply to Paul Wilde • • •Happens in firefox too on my mobile. I'm using Qutebrowser on my laptop.
If I search FreeBSD and then click on the FreeBSD Project URL which is freebsd.org I get the 400 bad request but the link showing is:
duckduckgo.com/l/?uddg=https%3…
social elephant in the room
in reply to Justine Smithies • • •social elephant in the room
in reply to social elephant in the room • • •Justine Smithies
in reply to social elephant in the room • • •Nope no box named freebsd on my network. It doesn't just happen with that search term it can be any search term. I tried and get the same results.
For example I just searched Gargening and clicked on gardenersworld.com but get the same 400 bad request. The link I copied from that result is :
duckduckgo.com/l/?uddg=https%3…
If I do the same from bing or google or whatever it all works. This just affects #DuckDuckGo for some reason ???
social elephant in the room
in reply to Justine Smithies • • •eerrr, this is odd...
and if you add this directly :
duckduckgo.com/?t=ftsa&q=FreeB…
Justine Smithies
in reply to social elephant in the room • • •Nginx
social elephant in the room
in reply to Justine Smithies • • •Justine Smithies
in reply to social elephant in the room • • •Justine Smithies
in reply to social elephant in the room • • •╰> dig +short duckduckgo.com
52.142.124.215
social elephant in the room
in reply to Justine Smithies • • •it returns me the same ip...
what about dns settings in (I assume) firefox?
Justine Smithies
in reply to social elephant in the room • • •Hmm hang on firefox on my mobile is working. It seems its just affecting Qutebrowser but only with DDG search requests ?? Very strange as I haven't changed any settings and it all worked yesterday. Away to check some network settings on my laptop incase an update has done something.
CC: @justine@mastodon.sdf.org
Justine Smithies
in reply to Justine Smithies • • •Right so it's a #Qutebrowser issue. Just installed #Firefox on this laptop and everything works.
The strange thing is on Qutebrowser I can click and view on the Report Ad URL's but if I click on any other return results I get the 400 Bad request Nginx. Using Firefox and all is good. I wonder what has happened to my trusty Qutebrowser ???
CC: @tseitr@mastodon.sdf.org @justine@mastodon.sdf.org
silverwizard
in reply to Justine Smithies • •@Justine Smithies Fascinating - that link causes a 400 for me - but searching for "gardener's world" with DDG lets me go there.
What's the network tab in the firefox dev tools saying? It seems like something is wrapping your clicks and it's out of date maybe?
Justine Smithies
in reply to silverwizard • • •silverwizard
in reply to Justine Smithies • •@Justine Smithies Oh I'd misread - sorry.
That's wilder.
That sounds like there's a redirect that is getting eaten by escaping somewhere. Is there any debug output?
(I tried qute recently... but it was too slow for my... not a sensible computer)
Justine Smithies
in reply to silverwizard • • •Justine Smithies
in reply to Justine Smithies • • •[ UPDATE ]
Finally I have tracked down my #Qutebrowser issue that only seemed to mess with #DuckDuckGo search results returning an
400 Bad Request
It seems in my
config.py
I had the following user agent line.c.content.headers.user_agent = 'Mozilla/5.0 ({os_info}) QtWebEngine/{qt_version} qutebrowser/{qutebrowser_version} Chromium/67.0.1'
I changed it to the same as #Firefox was using and bingo it all works !
c.content.headers.user_agent = 'Mozilla/5.0 (X11; Linux x86_64; rv:131.0) Gecko/20100101 Firefox/131.0'
Who's a happy bunny now.
I have now changed the original user agent to the following and all seems good.
c.content.headers.user_agent = 'Mozilla/5.0 ({os_info}) QtWebEngine/{qt_version} qutebrowser/{qutebrowser_version} Chrome/130.0.0.0'
CC: @silverwizard@convenient.email
silverwizard likes this.
silverwizard
in reply to Justine Smithies • •like this
Justine Smithies likes this.
Justine Smithies
Unknown parent • • •Justine Smithies
Unknown parent • • •Justine Smithies
Unknown parent • • •There was but that was on the 8th and it was working until yesterday or today ??
CC: @tseitr@mastodon.sdf.org @justine@mastodon.sdf.org
Justine Smithies
Unknown parent • • •Don't know just going through all the settings and there's loads ?
CC: @tseitr@mastodon.sdf.org @justine@mastodon.sdf.org
sndr
in reply to Justine Smithies • • •#170 Portal Updates · This Week in GNOME
thisweek.gnome.orgJustine Smithies
in reply to sndr • • •