On Tue, Mar 04, 2025 at 07:09:52AM GMT, Rene Kita wrote: > On Tue, Mar 04, 2025 at 12:43:47AM +0100, Joel Carnat wrote: > > Hi, > > > > I am publishing a SearXNG instance using relayd. It works properly with > > various graphical Web browsers and some text browsers. But when using > > w3m, the search doesn't work. If I replace relayd with nginx, the search > > works properly with w3m. > [...] > > When using `links http://example.com/`, the search works. > [...] > > tcpdump listening for POST queries displays: > > ======================================================================== > [...] > > .POST /searxng/search HTTP/1.1 > ^^^ > [...] > > When using `w3m http://example.com/`, the search doesn't work. > > w3m gets a blank page as the response of its POSTs. > [...] > > e./6,...POST /searxng/search HTTP/1.0 > ^^^ > > I wonder if the HTTP version in the POST request makes a difference > here.
I couldn't find a way to force w3m using HTTP/1.1. But using HTTP/1.0 with Links (`links -http-bugs.http10 1`) does not trigger the POST issue.
