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 #1257] [BUG] Response from Mullvad Leta needs cleanup #740

New issue

Closed

opened 2026-02-25 20:36:27 +03:00 by kerem · 5 comments

kerem commented

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

Owner

Originally created by @erusc on GitHub (Oct 4, 2025).
Original GitHub issue: https://github.com/benbusby/whoogle-search/issues/1257

Describe the bug
It seems that the HTML response from Mullvad Leta is currently injected directly in to the page without cleanup.
As a result, the browser renders the page in quirks mode and sends requests for nonexistent resources such as /fonts/OpenSans-Regular.woff2, /fonts/SourceSans-Semibold.woff2.

<html lang="en">
<head>
<meta charset="utf-8"/>
<meta content="width=device-width, initial-scale=1" name="viewport"/>
<meta content="#192e45" name="theme-color"/>
<link as="font" crossorigin="" href="/fonts/OpenSans-Regular.woff2" rel="preload" type="font/woff2"/>
<link as="font" crossorigin="" href="/fonts/SourceSans-Semibold.woff2" rel="preload" type="font/woff2"/>
<link href="/opensearch.xml" rel="search" title="Mullvad Leta" type="application/opensearchdescription+xml"/>
<link href="/favicon.ico" rel="icon" sizes="48x48"/>
<link href="./favicon.svg" rel="icon" sizes="any" type="image/svg+xml"/>
<link href="./apple-touch-icon.png" rel="apple-touch-icon" sizes="180x180"/>
<link href="./manifest.webmanifest" rel="manifest"/>
<link href="./_app/immutable/assets/0.D-xcUp6O.css" rel="stylesheet"/>
<link href="./_app/immutable/assets/KeyboardShortcutsTable.Df_QwWwk.css" rel="stylesheet"/>
<link href="./_app/immutable/assets/Navbar.BILx_08l.css" rel="stylesheet"/>
<link href="./_app/immutable/assets/3.DmlAQdvg.css" rel="stylesheet"/>
<link href="./_app/immutable/assets/SearchForm.-WKe5vqs.css" rel="stylesheet"/>
<link href="./_app/immutable/assets/9.CpS9TB5_.css" rel="stylesheet"/><!--[--><meta content="Leta, the privacy-focused search engine, by Mullvad." name="description"/> <link href="https://leta.mullvad.net/search" rel="canonical"/> <meta content="Mullvad Leta" property="og:title"/> <meta content="https://leta.mullvad.net/MullvadVPN_logo_Round_RGB_Color_positive.png" property="og:image"/> <meta content="Mullvad Leta" property="og:site_name"/> <meta content="website" property="og:type"/> <meta content="https://leta.mullvad.net/search?q=inpet&amp;engine=google" property="og:url"/> <meta content="Mullvad Leta" name="twitter:title"/> <meta content="summary" name="twitter:card"/> <meta content="@mullvadnet" name="twitter:creator"/> <meta content="https://leta.mullvad.net/MullvadVPN_logo_Round_RGB_Color_positive.png" name="twitter:image"/> <meta content="@mullvadnet" name="twitter:site"/><!--]--><!--[--><!--]--><title><b>inpet</b> - Mullvad Leta</title>
</head>

To Reproduce
Steps to reproduce the behavior:

Searh with any keyword.
Press F12 to show DevTools.
Go to Network Pane.
Check 404 errors.

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 1.1.0
Not sure

Desktop (please complete the following information):

OS: Windows
Browser: Firefox
Version: 143

Originally created by @erusc on GitHub (Oct 4, 2025). Original GitHub issue: https://github.com/benbusby/whoogle-search/issues/1257 **Describe the bug** It seems that the HTML response from Mullvad Leta is currently injected directly in to the page without cleanup. As a result, the browser renders the page in quirks mode and sends requests for nonexistent resources such as `/fonts/OpenSans-Regular.woff2`, `/fonts/SourceSans-Semibold.woff2`. ```html <html lang="en"> <head> <meta charset="utf-8"/> <meta content="width=device-width, initial-scale=1" name="viewport"/> <meta content="#192e45" name="theme-color"/> <link as="font" crossorigin="" href="/fonts/OpenSans-Regular.woff2" rel="preload" type="font/woff2"/> <link as="font" crossorigin="" href="/fonts/SourceSans-Semibold.woff2" rel="preload" type="font/woff2"/> <link href="/opensearch.xml" rel="search" title="Mullvad Leta" type="application/opensearchdescription+xml"/> <link href="/favicon.ico" rel="icon" sizes="48x48"/> <link href="./favicon.svg" rel="icon" sizes="any" type="image/svg+xml"/> <link href="./apple-touch-icon.png" rel="apple-touch-icon" sizes="180x180"/> <link href="./manifest.webmanifest" rel="manifest"/> <link href="./_app/immutable/assets/0.D-xcUp6O.css" rel="stylesheet"/> <link href="./_app/immutable/assets/KeyboardShortcutsTable.Df_QwWwk.css" rel="stylesheet"/> <link href="./_app/immutable/assets/Navbar.BILx_08l.css" rel="stylesheet"/> <link href="./_app/immutable/assets/3.DmlAQdvg.css" rel="stylesheet"/> <link href="./_app/immutable/assets/SearchForm.-WKe5vqs.css" rel="stylesheet"/> <link href="./_app/immutable/assets/9.CpS9TB5_.css" rel="stylesheet"/><meta content="Leta, the privacy-focused search engine, by Mullvad." name="description"/> <link href="https://leta.mullvad.net/search" rel="canonical"/> <meta content="Mullvad Leta" property="og:title"/> <meta content="https://leta.mullvad.net/MullvadVPN_logo_Round_RGB_Color_positive.png" property="og:image"/> <meta content="Mullvad Leta" property="og:site_name"/> <meta content="website" property="og:type"/> <meta content="https://leta.mullvad.net/search?q=inpet&engine=google" property="og:url"/> <meta content="Mullvad Leta" name="twitter:title"/> <meta content="summary" name="twitter:card"/> <meta content="@mullvadnet" name="twitter:creator"/> <meta content="https://leta.mullvad.net/MullvadVPN_logo_Round_RGB_Color_positive.png" name="twitter:image"/> <meta content="@mullvadnet" name="twitter:site"/><title><b>inpet</b> - Mullvad Leta</title> </head> ``` **To Reproduce** Steps to reproduce the behavior: 1. Searh with any keyword. 2. Press F12 to show DevTools. 3. Go to Network Pane. 4. Check 404 errors. **Deployment Method** - [ ] Heroku (one-click deploy) - [x] Docker - [ ] `run` executable - [ ] pip/pipx - [ ] Other: [describe setup] **Version of Whoogle Search** - [ ] Latest build from [source] (i.e. GitHub, Docker Hub, pip, etc) - [x] Version 1.1.0 - [ ] Not sure **Desktop (please complete the following information):** - OS: Windows - Browser: Firefox - Version: 143

kerem

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

closed this issue
added the
bug
label

kerem commented

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

Author

Owner

@Don-Swanson commented on GitHub (Oct 5, 2025):

Thanks for this. Would you consider this to be a major or critical flaw that prevents this stopgap release from continuing to operate until a better solution is developed?

@Don-Swanson commented on GitHub (Oct 5, 2025): Thanks for this. Would you consider this to be a major or critical flaw that prevents this stopgap release from continuing to operate until a better solution is developed?

kerem commented

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

Author

Owner

@meijkl commented on GitHub (Oct 8, 2025):

Thanks for this. Would you consider this to be a major or critical flaw that prevents this stopgap release from continuing to operate until a better solution is developed?

Since there is no answer from @erusc just my comment - for me it's not a major or critical flaw, I'm happy to still being able to use Whoogle!

Thanks for your efforts!

Klaus

@meijkl commented on GitHub (Oct 8, 2025): > Thanks for this. Would you consider this to be a major or critical flaw that prevents this stopgap release from continuing to operate until a better solution is developed? Since there is no answer from @erusc just my comment - for me it's not a major or critical flaw, I'm happy to still being able to use Whoogle! Thanks for your efforts! Klaus

kerem commented

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

Author

Owner

@Don-Swanson commented on GitHub (Oct 8, 2025):

@meijkl
Can you please elaborate how this is a major flaw and what it is preventing?

To me this appears to be cosmetic and an annoyance. Since this is only considered to be a stopgap release, do you think time should be spent on this instead of development of a permanent solution?

@Don-Swanson commented on GitHub (Oct 8, 2025): @meijkl Can you please elaborate how this is a major flaw and what it is preventing? To me this appears to be cosmetic and an annoyance. Since this is only considered to be a stopgap release, do you think time should be spent on this instead of development of a permanent solution?

kerem commented

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

Author

Owner

@meijkl commented on GitHub (Oct 8, 2025):

@meijkl Can you please elaborate how this is a major flaw and what it is preventing?

To me this appears to be cosmetic and an annoyance. Since this is only considered to be a stopgap release, do you think time should be spent on this instead of development of a permanent solution?

I think you misunderstood my comment - for me it is NOT a major flaw!
What I typically need works with the current version!

Time should be spent for the development of a permanent solution.

@meijkl commented on GitHub (Oct 8, 2025): > [@meijkl](https://github.com/meijkl) Can you please elaborate how this is a major flaw and what it is preventing? > > To me this appears to be cosmetic and an annoyance. Since this is only considered to be a stopgap release, do you think time should be spent on this instead of development of a permanent solution? I think you misunderstood my comment - for me it is NOT a major flaw! What I typically need works with the current version! Time should be spent for the development of a permanent solution.

kerem commented

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

Author

Owner

@Don-Swanson commented on GitHub (Oct 8, 2025):

My apologies, that’s what I get when I check my emails too early.

@Don-Swanson commented on GitHub (Oct 8, 2025): My apologies, that’s what I get when I check my emails too early.