starred/whoogle-search

Fork 0

mirror of https://github.com/benbusby/whoogle-search.git synced 2026-04-25 04:05:57 +03:00

[GH-ISSUE #153] [BUG] no succesful enforcing of HTTPS on Heroku #114

New issue

Closed

opened 2026-02-25 20:34:55 +03:00 by kerem · 4 comments

kerem commented

2026-02-25 20:34:55 +03:00

Owner

Originally created by @pred2k on GitHub (Dec 5, 2020).
Original GitHub issue: https://github.com/benbusby/whoogle-search/issues/153

Describe the bug
I would like to have a all search requests and reponses to go though HTTPS.
HTTP requests should be upgrade to HTTPS.

To Reproduce
Steps to reproduce the behavior:

Open new private window in Firefox (also open network analytics from web developer tools to see detailed behaviour)
Go go g00gl3.herokuapp.com (no https!)
Open Configuration and see that the Root URL begins with https://...
Now search for anything and see that everything is transfered unencrypted

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) - commit 54109874fb
Version [version number]
Not sure

Desktop (please complete the following information):

OS: MacOS Catalina 10.15.5
Browser: Firefox
Version: 82.0.2 (64bit)

Additional context
I've tried to have the ROOT URL (and search language) to be constant in the heroku dyno with having this cronjob:

curl -d "ctry=&lang_interface=&lang_search=lang_de&near=&alts=on&url=https%3A%2F%2Fg00gl3.herokuapp.com%2F" https://g00gl3.herokuapp.com/config

Originally created by @pred2k on GitHub (Dec 5, 2020). Original GitHub issue: https://github.com/benbusby/whoogle-search/issues/153 **Describe the bug** I would like to have a all search requests and reponses to go though HTTPS. HTTP requests should be upgrade to HTTPS. **To Reproduce** Steps to reproduce the behavior: 1. Open new private window in Firefox (also open network analytics from web developer tools to see detailed behaviour) 2. Go go `g00gl3.herokuapp.com` (no https!) 3. Open **Configuration** and see that the **Root URL** begins with `https://...` 4. Now search for anything and see that everything is transfered unencrypted ![Bildschirmfoto 2020-12-05 um 12 03 34](https://user-images.githubusercontent.com/1071020/101240928-b9ac6280-36f2-11eb-8f88-59e6923c68c8.png) **Deployment Method** - [x] Heroku (one-click deploy) - [ ] Docker - [ ] `run` executable - [ ] pip/pipx - [ ] Other: [describe setup] **Version of Whoogle Search** - [x] Latest build from [source] (i.e. GitHub, Docker Hub, pip, etc) - **commit 54109874fb312f174eb5c65795c62760f65f87de** - [ ] Version [version number] - [ ] Not sure **Desktop (please complete the following information):** - OS: **MacOS Catalina 10.15.5** - Browser: **Firefox** - Version: **82.0.2 (64bit)** **Additional context** I've tried to have the **ROOT URL** (and search language) to be constant in the heroku dyno with having this cronjob: ``` curl -d "ctry=&lang_interface=&lang_search=lang_de&near=&alts=on&url=https%3A%2F%2Fg00gl3.herokuapp.com%2F" https://g00gl3.herokuapp.com/config ```

kerem

2026-02-25 20:34:55 +03:00

closed this issue
added the
bug
label

kerem commented

2026-02-25 20:34:56 +03:00

Author

Owner

@benbusby commented on GitHub (Dec 5, 2020):

Thanks for reporting! HTTPS enforcement on Heroku has been an issue in the past. The commit referenced above should fix this once and for all. I tested it on my end to confirm that it's always upgrading now, but let me know if you see this happen again.

@benbusby commented on GitHub (Dec 5, 2020): Thanks for reporting! HTTPS enforcement on Heroku has been an issue in the past. The commit referenced above should fix this once and for all. I tested it on my end to confirm that it's always upgrading now, but let me know if you see this happen again.

kerem commented

2026-02-25 20:34:56 +03:00

Author

Owner

@pred2k commented on GitHub (Dec 6, 2020):

Yeah! Looks great now, thanks mate

@pred2k commented on GitHub (Dec 6, 2020): Yeah! Looks great now, thanks mate

kerem commented

2026-02-25 20:34:56 +03:00

Author

Owner

@pred2k commented on GitHub (Dec 18, 2020):

i dont know why, but g00gl3.herokuapp.com behaves again like in my initial post. stays on unencrypted http.
its on 6e7ec9918a now

@pred2k commented on GitHub (Dec 18, 2020): i dont know why, but g00gl3.herokuapp.com behaves again like in my initial post. stays on unencrypted http. its on 6e7ec9918a7bb04b8d78358ea5dd2315a1b9a3eb now

kerem commented

2026-02-25 20:34:56 +03:00

Author

Owner

@benbusby commented on GitHub (Dec 18, 2020):

Hmm, I just launched a new herokuapp instance of my own, and it seems to working fine and upgrading automatically. Also http://g00gl3.herokuapp.com is upgrading to https for me. You could try the latest commit on the heroku-app-beta branch, but it shouldn't be any different.

@benbusby commented on GitHub (Dec 18, 2020): Hmm, I just launched a new herokuapp instance of my own, and it seems to working fine and upgrading automatically. Also http://g00gl3.herokuapp.com is upgrading to https for me. You could try the latest commit on the `heroku-app-beta` branch, but it shouldn't be any different.

kerem referenced this issue

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

[PR #114] [MERGED] Allow for free deployment to Repl.it #787

kerem referenced this issue

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

[PR #116] [MERGED] v0.2.1 #791