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

Extend proxy policy features in Azure Core #3121

Closed
1 task done
jeremymeng opened this issue May 22, 2019 · 3 comments
Closed
1 task done

Extend proxy policy features in Azure Core #3121

jeremymeng opened this issue May 22, 2019 · 3 comments
Labels
Azure.Core Client This issue points to a problem in the data-plane of the library.

Comments

@jeremymeng
Copy link
Member

jeremymeng commented May 22, 2019

there's a proxy policy in ms-rest-js. However it lacks support for

also it doesn't consider the scheme (http or https) used in current connection it already handles this.

@jeremymeng jeremymeng added this to the Sprint 155 milestone May 22, 2019
@kurtzeborn kurtzeborn added Client This issue points to a problem in the data-plane of the library. Storage Storage Service (Queues, Blobs, Files) labels May 24, 2019
@jeremymeng
Copy link
Member Author

Post preview 1

@ramya-rao-a
Copy link
Contributor

ramya-rao-a commented Dec 16, 2019

Notes from Azure Core triage meeting:

Follow up: Check proxy support implemented for Event Hubs

@ramya-rao-a ramya-rao-a changed the title Pipeline - proxy policy Extend proxy policy features in Azure Core Dec 16, 2019
@xirzec xirzec modified the milestones: [2020] February, Backlog Feb 11, 2020
@ramya-rao-a
Copy link
Contributor

Pending task is around message digest for which there is no user feedback/interest at the moment. So, closing

@xirzec xirzec removed this from the Backlog milestone May 18, 2022
@github-actions github-actions bot locked and limited conversation to collaborators Apr 12, 2023
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
Azure.Core Client This issue points to a problem in the data-plane of the library.
Projects
None yet
Development

No branches or pull requests

5 participants