[GH-ISSUE #1026] [BUG] How to go back to search session after clicking a link #630

New issue

Closed

opened 2026-02-25 20:36:10 +03:00 by kerem · 1 comment

kerem commented

2026-02-25 20:36:10 +03:00

Owner

Originally created by @mysteriousHerb on GitHub (Jun 25, 2023).
Original GitHub issue: https://github.com/benbusby/whoogle-search/issues/1026

Use both the self-hosted docker version of the https://w.ftw.lol/search, whenever you search something and go into the link and "go back" on browser, the chrome or edge will both compalin about "Confirm Form Resubmission" and "ERR_CACHE_MISS"

Deployment Method

Heroku (one-click deploy)
Docker
run executable
pip/pipx
Other: [describe setup]

Version of Whoogle Search

Latest build from [source] (i.e. GitHub, Docker Hub, pip, etc)
Version [version number]
Not sure

Desktop (please complete the following information):

OS: windows 10
Browser: chrome and edge
Version [e.g. 22]

Originally created by @mysteriousHerb on GitHub (Jun 25, 2023). Original GitHub issue: https://github.com/benbusby/whoogle-search/issues/1026 Use both the self-hosted docker version of the https://[w.ftw.lol](https://w.ftw.lol/search)/search, whenever you search something and go into the link and "go back" on browser, the chrome or edge will both compalin about "Confirm Form Resubmission" and "ERR_CACHE_MISS" **Deployment Method** - [ ] Heroku (one-click deploy) - [x] Docker - [ ] `run` executable - [ ] pip/pipx - [ ] Other: [describe setup] **Version of Whoogle Search** - [x] Latest build from [source] (i.e. GitHub, Docker Hub, pip, etc) - [ ] Version [version number] - [ ] Not sure **Desktop (please complete the following information):** - OS: windows 10 - Browser: chrome and edge - Version [e.g. 22]

kerem

2026-02-25 20:36:10 +03:00

closed this issue
added the
bug
label

kerem commented

2026-02-25 20:36:11 +03:00

Author

Owner

@benbusby commented on GitHub (Jun 26, 2023):

This happens due to Whoogle using POST requests for search by default. You can get around this by enabling "GET Requests Only" in your config on the homepage.

@benbusby commented on GitHub (Jun 26, 2023): This happens due to Whoogle using POST requests for search by default. You can get around this by enabling "GET Requests Only" in your config on the homepage.