8000 Consider adding support for custom HttpRequest for remote APIs · Issue #209 · oras-project/oras-dotnet · GitHub
[go: up one dir, main page]
More Web Proxy on the site http://driver.im/
Skip to content

Consider adding support for custom HttpRequest for remote APIs #209

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

Open
1 task
9356
akashsinghal opened this issue May 6, 2025 · 0 comments
Open
1 task
Labels
enhancement New feature or request triage New issues or PRs to be acknowledged by maintainers

Comments

@akashsinghal
Copy link

What is the version or commit of the ORAS .NET library?

No response

What would you like to be added?

The remote APIs defined for remote Registry and Repository create a new HttpRequest per invocation. It would be helpful if a parameter to pass in a HttpRequest object could be specified. This is helpful when the request context is altered. For example, in my use case I leverage Polly policies that add retry and auth capabilities (+ caching). This context is set per HttpRequest

Why is this needed for the ORAS .NET library?

Given the lack of robust authentication capabilities and built-in retry mechanisms, it would be good to allow SDK clients the flexibility to implement and integrate with ORAS.

Are you willing to submit PRs to contribute to this feature?

  • Yes, I am willing to implement it.
@akashsinghal akashsinghal added enhancement New feature or request triage New issues or PRs to be acknowledged by maintainers labels May 6, 2025
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
enhancement New feature or request triage New issues or PRs to be acknowledged by maintainers
Projects
None yet
Development

No branches or pull requests

1 participant
0