mirror of
https://github.com/benbusby/whoogle-search.git
synced 2026-04-25 12:15:50 +03:00
[GH-ISSUE #708] [QUESTION] Search not executed at once as default search engine #453
Labels
No labels
Fixed (Pending PR Merge)
Stale
bug
enhancement
enhancement
good first issue
help wanted
keep-open
needs more info
pull-request
question
theme
unfortunate
No milestone
No project
No assignees
1 participant
Notifications
Due date
No due date set.
Dependencies
No dependencies set.
Reference
starred/whoogle-search#453
Loading…
Add table
Add a link
Reference in a new issue
No description provided.
Delete branch "%!s()"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
Originally created by @ludoctl on GitHub (Apr 2, 2022).
Original GitHub issue: https://github.com/benbusby/whoogle-search/issues/708
Hey y'all,
Maybe an easy one, but been looking around without success so far: I added my self hosted, docker-behind-nginx-reverse-proxy-with-SSL whoogle instance as default search engine on my ubuntu 21.10 FF 98.0.2, but when typing in the URL bar it doesn't give me the search results, it just goes to my whoogle homepage and I have to type it again.
WHY? :)
Let me what info I can add to debunk this if anything!
@cedriking commented on GitHub (Apr 11, 2022):
I just installed whoogle through Docker. I'm having the same issue while using docker and traefik.
I tried manually adding
/search?q=asdfto my own instance and it works. So the issue seems related to the way Firefox save this when usingAdd "Whoogle"from the navigation bar.@ShlomiD83 commented on GitHub (Apr 14, 2022):
https://path.to.whoogle/search?q=%s
this setup works for me.
@cedriking commented on GitHub (Apr 14, 2022):
It's not possible to set this on Firefox desktop. Or at least I haven't found a way. That method is only for the mobile apps.
@DUOLabs333 commented on GitHub (May 25, 2022):
It works for me.
@worldofgeese commented on GitHub (Jul 9, 2022):
I have started to experience this in the last docker image push. I cannot set https://path.to.whoogle/search?q=%s on Firefox desktop (you can but it requires deconstructing a JS file which you have to do every update).
Any logs we can provide to help track this down? I rely on Whoogle a lot and the extra friction from entering search queries twice is significant.
@benbusby commented on GitHub (Aug 1, 2022):
Can anyone experiencing this issue post the contents of
/opensearch.xmlwhen visiting from an affected browser? It's likely an issue with the opensearch template, but I haven't been able to track it down on my end.@hugues999 commented on GitHub (Aug 2, 2022):
I have the same issue, with both Firefox and chromium based browsers. I can reproduce it by opening incognito mode and browsing to https://whoogle-path/search?q=something. First time it will fail, and after that it will work as long as I don't restart the browser or the incognito window. The initial request returns an HTTP 307 (temporary redirect) but the browser doesn't seem to follow it.
Here is my opensearch.xml:
@benbusby commented on GitHub (Aug 2, 2022):
@hugues999 I'm unfortunately not able to recreate it with those steps either (on Firefox or a Chromium based browser).
I think there's two possibilities for what's going on. Either new sessions aren't able to successfully lock in a new session ID when performing searches through opensearch, and so the session validation step fails and sends the user back to the home page, or the session validation step just doesn't work altogether for some users.
It's a little hard to debug since I still can't reproduce this, but I'll look into potential solutions soon. If anything, I could at least provide a way to turn off session validation (which would remove any redirects for new sessions), which would likely only pose a risk to public instance maintainers anyways.
Edit: Never mind, I was able to figure out the issue using one of the public instances. I should have a fix pushed soon.
@benbusby commented on GitHub (Aug 2, 2022):
OK, I believe this should be fixed by the changes I just pushed. Basically new session searches weren't being fully reconstructed with the correct path, so initial searches would be redirected back to the home page. If anyone wants to try the latest changes on
mainor thelatestDocker tag (once it's updated) and let me know if that fixes the issue, that would be great!@hugues999 commented on GitHub (Aug 2, 2022):
@benbusby I tested the latest docker image and it looks like the issue is fixed, thanks for your help 👍