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

routing/http/client: allow custom User-Agent #17

Closed
2 tasks done
lidel opened this issue Dec 9, 2022 · 0 comments · Fixed by #31
Closed
2 tasks done

routing/http/client: allow custom User-Agent #17

lidel opened this issue Dec 9, 2022 · 0 comments · Fixed by #31
Assignees
Labels
effort/hours Estimated to take one or several hours kind/maintenance Work required to avoid breaking changes or harm to project's status quo P1 High: Likely tackled by core team if no one steps up

Comments

@lidel
Copy link
Member

lidel commented Dec 9, 2022

Currently, routing/http/client sends requests with generic User-Agent: Go-http-client/1.1 from golang's http package.

Before we ship with Kubo 0.18, this library should:

  • Change implicit default to own User-Agent: go-libipfs/routing/http/client[/version]
  • Allow Kubo for passing own version string via func WithUserAgent(ua string) option
    • We want IPNI at cid.contact to know which versions of Kubo are sending requests, to make informed decision about supporting legacy endpoints, making breaking changes etc. (cc @willscott)
@lidel lidel added the need/triage Needs initial labeling and prioritization label Dec 9, 2022
@ipfs ipfs deleted a comment from welcome bot Dec 9, 2022
lidel added a commit that referenced this issue Jan 14, 2023
lidel added a commit to ipfs/kubo that referenced this issue Jan 14, 2023
lidel added a commit to ipfs/kubo that referenced this issue Jan 14, 2023
@lidel lidel self-assigned this Jan 14, 2023
@lidel lidel added P1 High: Likely tackled by core team if no one steps up effort/hours Estimated to take one or several hours kind/maintenance Work required to avoid breaking changes or harm to project's status quo and removed need/triage Needs initial labeling and prioritization labels Jan 14, 2023
@lidel lidel closed this as completed in #31 Jan 17, 2023
lidel added a commit to ipfs/kubo that referenced this issue Jan 17, 2023
lidel added a commit to ipfs/kubo that referenced this issue Jan 18, 2023
lidel added a commit to ipfs/kubo that referenced this issue Jan 18, 2023
lidel added a commit to ipfs/kubo that referenced this issue Jan 18, 2023
galargh pushed a commit to ipfs/kubo that referenced this issue Jan 23, 2023
hannahhoward pushed a commit to filecoin-project/kubo-api-client that referenced this issue Jun 19, 2023
hannahhoward pushed a commit to filecoin-project/kubo-api-client that referenced this issue Jun 19, 2023
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
effort/hours Estimated to take one or several hours kind/maintenance Work required to avoid breaking changes or harm to project's status quo P1 High: Likely tackled by core team if no one steps up
Projects
None yet
Development

Successfully merging a pull request may close this issue.

1 participant