bug: improving.duckduckgo.com is not blocked even `block_trackers: true` exist

Open
#83 0 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Assessment

Difficulty
3/5
Estimated time
1-2 days
Newbie friendliness
35/100
Issue type
Bug
Clarity
Mostly clear
Activity status
Active
Tech stack
go
Domain
search

Research direction

The request to improving.duckduckgo.com comes from the browser-mode DuckDuckGo engine in the openserp Go codebase, so start by finding where the browser retrieval path sets up request interception or the block_trackers option. Check whether the blocklist covers that host and why it is missed. Done means the host is blocked when block_trackers is enabled, verified by a request log from a DuckDuckGo search run.

Written by the indexing model from the issue text.

Description

bug
What happened?

I'm blocking improving.duckduckgo.com at SOCKS proxy; openserp's chromium does request improving.duckduckgo.com. Duckduckgo can be used without it, why this "tracker" is not blocked?

How do we reproduce it?
  1. Use openserp to search anything with duckduckgo endpoint.
  2. Observe traffic.
Retrieval mode

browser

Engine

duckduckgo

OpenSERP version

0.8.19

Environment

Linux, Release https://github.com/karust/openserp/releases/tag/v0.8.19

Logs or response body

Dominant language
Go
Stars
1.5k
Forks
173
Avg merge
7d 5h
Merged PRs (30d)
4

Getting set up

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

More from karust/openserp

All issues in karust/openserp

Similar issues

More Go issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.