starred/whoogle-search

Fork 0

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

to the URL, so an invalid redirect happens #394

New issue

Closed

opened 2026-02-25 20:35:38 +03:00 by kerem · 7 comments

kerem commented

2026-02-25 20:35:38 +03:00

Owner

Originally created by @dr460nf1r3 on GitHub (Jan 18, 2022).
Original GitHub issue: https://github.com/benbusby/whoogle-search/issues/614

Describe the bug
After hitting apply when changing settings, the page gets redirected to a not existing URL: https://search.garudalinux.org/%22https://%22https://%22https://%22https://%22https://%22https://%22https://%22https://%22https://%22https://search.garudalinux.org%22

To Reproduce
Steps to reproduce the behavior:

Go to Garudas Whoogle instance
Any settings
Hit apply
Get redirected to nowhere

Deployment Method

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

Version of Whoogle Search

Latest Docker image
Version 0.7.0
Not sure

Desktop (please complete the following information):

OS: [Linux]
Browser [FireDragon]
Version [96.0.1]

Smartphone (please complete the following information):

Device: [Pixel 6]
OS: [ProtonAOSP 12]
Browser [Kiwi Browser, Bromite]
Version [98, 96]

Additional information:
The following docker-compose.yml is used:

  whoogle_search:
    image: benbusby/whoogle-search:latest
    container_name: whoogle_search
    restart: always
    environment:
      - WHOOGLE_CONFIG_URL="https://search.garudalinux.org"

Originally created by @dr460nf1r3 on GitHub (Jan 18, 2022). Original GitHub issue: https://github.com/benbusby/whoogle-search/issues/614 **Describe the bug** After hitting apply when changing settings, the page gets redirected to a not existing URL: `https://search.garudalinux.org/%22https://%22https://%22https://%22https://%22https://%22https://%22https://%22https://%22https://%22https://search.garudalinux.org%22` **To Reproduce** Steps to reproduce the behavior: 1. Go to [Garudas Whoogle instance](https://search.garudalinux.org/) 2. Any settings 3. Hit `apply` 4. Get redirected to nowhere **Deployment Method** - [ ] Heroku (one-click deploy) - [x] Docker - [ ] `run` executable - [ ] pip/pipx - [ ] Other: [describe setup] **Version of Whoogle Search** - [x] Latest Docker image - [ ] Version 0.7.0 - [ ] Not sure **Desktop (please complete the following information):** - OS: [Linux] - Browser [FireDragon] - Version [96.0.1] **Smartphone (please complete the following information):** - Device: [Pixel 6] - OS: [ProtonAOSP 12] - Browser [Kiwi Browser, Bromite] - Version [98, 96] **Additional information:** The following docker-compose.yml is used: ```yaml whoogle_search: image: benbusby/whoogle-search:latest container_name: whoogle_search restart: always environment: - WHOOGLE_CONFIG_URL="https://search.garudalinux.org" ```

kerem

2026-02-25 20:35:38 +03:00

closed this issue
added the
bug
label

kerem commented

2026-02-25 20:35:38 +03:00

Author

Owner

@Albonycal commented on GitHub (Jan 24, 2022):

  - WHOOGLE_CONFIG_URL="https://search.garudalinux.org"

is that env variable necessary?
doesn't it automatically set that

@Albonycal commented on GitHub (Jan 24, 2022): > - WHOOGLE_CONFIG_URL="https://search.garudalinux.org" is that env variable necessary? doesn't it automatically set that

kerem commented

2026-02-25 20:35:38 +03:00

Author

Owner

@dr460nf1r3 commented on GitHub (Jan 24, 2022):

I don't know, I assumed it was since the instance tried to load a CSS file via http instead https. When using a browser with https only mode enabled this gives an ugly warning :/

@dr460nf1r3 commented on GitHub (Jan 24, 2022): I don't know, I assumed it was since the instance tried to load a CSS file via http instead https. When using a browser with https only mode enabled this gives an ugly warning :/

kerem commented

2026-02-25 20:35:38 +03:00

Author

Owner

@Albonycal commented on GitHub (Jan 24, 2022):

hmm, I have also noticed this redirect error, but I ignored it because the settings apply

@Albonycal commented on GitHub (Jan 24, 2022): hmm, I have also noticed this redirect error, but I ignored it because the settings apply

kerem commented

2026-02-25 20:35:38 +03:00

Author

Owner

@dr460nf1r3 commented on GitHub (Jan 24, 2022):

It it still quite a bummer if this happens when showing people the search engine :/

Maybe I should create another issue for that, since it happens a lot?

@dr460nf1r3 commented on GitHub (Jan 24, 2022): It it still quite a bummer if this happens when showing people the search engine :/ Maybe I should create another issue for that, since it happens a lot?

kerem commented

2026-02-25 20:35:38 +03:00

Author

Owner

@benbusby commented on GitHub (Jan 25, 2022):

@dr460nf1r3 on your instance I was able to fix the redirecting issue by removing the double quotes on either end of the root URL. It seems that somehow in setting the WHOOGLE_CONFIG_URL environment variable, the quotes were carried over, which creates an invalid URL when redirecting back to the home page (the root URL is used for redirecting all requests if overwritten).

It looks like only docker-compose keeps the quotes intact when setting a variable value, which is bizarre. Setting the variable outside of docker-compose with the quotes works as expected.

That being said, is there any more info you can provide regarding the CSS file that was loaded over http instead of https? I'm not able to replicate that issue either, but would like to investigate if you can send over a screenshot of the network requests when that file is loaded, or something to that effect.

@benbusby commented on GitHub (Jan 25, 2022): @dr460nf1r3 on your instance I was able to fix the redirecting issue by removing the double quotes on either end of the root URL. It seems that somehow in setting the `WHOOGLE_CONFIG_URL` environment variable, the quotes were carried over, which creates an invalid URL when redirecting back to the home page (the root URL is used for redirecting all requests if overwritten). It looks like only docker-compose keeps the quotes intact when setting a variable value, which is bizarre. Setting the variable outside of docker-compose with the quotes works as expected. That being said, is there any more info you can provide regarding the CSS file that was loaded over http instead of https? I'm not able to replicate that issue either, but would like to investigate if you can send over a screenshot of the network requests when that file is loaded, or something to that effect.

kerem commented

2026-02-25 20:35:38 +03:00

Author

Owner

@benbusby commented on GitHub (Feb 1, 2022):

Closing for now, but feel free to reopen if this is still happening even after removing the quotes from the root URL.

@benbusby commented on GitHub (Feb 1, 2022): Closing for now, but feel free to reopen if this is still happening even after removing the quotes from the root URL.

kerem commented

2026-02-25 20:35:38 +03:00

Author

Owner

@dr460nf1r3 commented on GitHub (Feb 1, 2022):

Hey @benbusby ! I somehow forgot to report back after testing the change. So yes, that resolved the issue with https redirects! :)

I actually wanted to provide you with some logs about the other issue, guess I'll just open another issue to do it properly.

@dr460nf1r3 commented on GitHub (Feb 1, 2022): Hey @benbusby ! I somehow forgot to report back after testing the change. So yes, that resolved the issue with https redirects! :) I actually wanted to provide you with some logs about the other issue, guess I'll just open another issue to do it properly.