double-encoding in serpapi_pagination.next?
Nobody has claimed this yet.
Assessment
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Newbie friendliness
- 45/100
Research direction
Start at the serpapi_pagination.next? pagination entry point and trace how its returned URL encodes the brand-filter pipes. Reproduce the reported %257C output and compare it with the expected single encoding; done means next? no longer double-encodes those pipes.
Written by the indexing model from the issue text.
Description
Per my llm:
Rewriting rh; your returned URL also double-encoded the brand-filter pipes as %257C
- Dominant language
- Go
- Stars
- 13
- Forks
- 4
- PR merge metrics
- No merged PRs in 30d
Contributor guide
No contributing guide indexed for this repository
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
More from serpapi/serpapi-cli
-
Difficulty 3/5 1-2 days Newbie friendliness 45/100
serpapi/serpapi-cli#12 ·
-
enhancement
Difficulty 3/5 1-2 days Newbie friendliness 55/100
serpapi/serpapi-cli#10 ·
-
serpapi/serpapi-cli#8 · 2 comments · 1 assignee ·
All issues in serpapi/serpapi-cli
Similar issues
-
optimization optimization:agents-md-curator
Difficulty 2/5 1-3 hours Newbie friendliness 86/100
githubnext/gh-aw-cao#13143 ·
-
Difficulty 2/5 1-3 hours Newbie friendliness 84/100
blinklabs-io/bursa#904 ·
-
Difficulty 2/5 1-3 hours Newbie friendliness 84/100
yanet-platform/ipfw-go#129 ·
-
bug confmap/provider/googlesecretmanagerprovider needs triage
Difficulty 2/5 1-3 hours Newbie friendliness 72/100
open-telemetry/opentelemetry-collector-contrib#51273 · 2 comments ·
-
bug: AI Gateway client filter lists "Unknown" twice when NULL and literal Unknown clients coexist Openbug
Difficulty 2/5 1-3 hours Newbie friendliness 90/100