Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Title: merklemap-cli search "example.com" not working #2

Open
5hank4r opened this issue Nov 7, 2024 · 3 comments
Open

Title: merklemap-cli search "example.com" not working #2

5hank4r opened this issue Nov 7, 2024 · 3 comments

Comments

@5hank4r
Copy link

5hank4r commented Nov 7, 2024

When running the command merklemap-cli search example.com, it fails to return any results or produces an error.

 merklemap-cli search "example.com" or  merklemap-cli search bing.com etc

Error: InvalidContentType("application/json", Response { url: "https://api.merklemap.com/search?query=example.com&stream=true&stream_progress=true", status: 200, headers: {"date": "Thu, 07 Nov 2024 08:23:44 GMT", "content-type": "application/json", "transfer-encoding": "chunked", "connection": "keep-alive", "access-control-allow-origin": "*", "vary": "origin, access-control-request-method, access-control-request-headers", "vary": "accept-encoding", "cf-cache-status": "DYNAMIC", "report-to": "{\"endpoints\":[{\"url\":\"https:\/\/a.nel.cloudflare.com\/report\/v4?s=6VbNUES9itcqIbbESsYgYO0Yj5LBC3rQygx74YYdpJcHIk70RHD9qbObBPwN8xrm4rWONUPrQGRhxIP0Vx6E9gv75jeSDoGqwXFIPf8OMogplz6ihs68gjLTD61cP8EHSBFN\"}],\"group\":\"cf-nel\",\"max_age\":604800}", "nel": "{\"success_fraction\":0,\"report_to\":\"cf-nel\",\"max_age\":604800}", "x-content-type-options": "nosniff", "server": "cloudflare", "cf-ray": "8debec4058ade1fc-MRS", "alt-svc": "h3=\":443\"; ma=86400", "server-timing": "cfL4;desc=\"?proto=TCP&rtt=140140&sent=5&recv=6&lost=0&retrans=0&sent_bytes=2830&recv_bytes=776&delivery_rate=29422&cwnd=249&unsent_bytes=0&cid=10a210a8f92a5748&ts=1040&x=0\""} })
@blackline1337
Copy link

The issue is the content type it seems. I have the same issue.

@Barre
Copy link
Collaborator

Barre commented Nov 24, 2024

This issue is due to backend modifications that removed stream=true functionality. While the initial API implementation used streaming as a quick solution, the current backend is significantly more efficient and can handle tens of requests per second from a single client without noticeable load.

I plan to publish an updated CLI version this week to reflect these changes.

@awetz
Copy link

awetz commented Dec 28, 2024

any update?

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

4 participants