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.

Sign up for GitHub

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

Jump to bottom

[core-http] Investigate retry error codes for XhrClient #9568

Closed
xirzec opened this issue Jun 16, 2020 · 2 comments
Closed

[core-http] Investigate retry error codes for XhrClient #9568

xirzec opened this issue Jun 16, 2020 · 2 comments
Labels
Azure.Core Client This issue points to a problem in the data-plane of the library.

Comments

@xirzec
Copy link
Member

xirzec commented Jun 16, 2020

Currently our policy for systemErrorRetry appears to only consider Node-raised errors for transient network issues / transport layer problems.

We should look at what happens in the browser and consider handling DOMException names for cases we might want to retry.
@xirzec xirzec added Client This issue points to a problem in the data-plane of the library. Azure.Core labels Jun 16, 2020
@xirzec xirzec added this to the Backlog milestone Jun 16, 2020
@xirzec xirzec mentioned this issue Jun 16, 2020
Merged
@jeremymeng
Copy link
Member

  • consider switching to Browser Fetch API
  • node also have fetch api coming
  • fold this work into Fetch work

@jeremymeng jeremymeng mentioned this issue Jul 13, 2021
Closed
1 task
@jeremymeng
Copy link
Member

Tracked in #16368. Closing this one.

@xirzec xirzec mentioned this issue Jul 15, 2021
Closed
@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.
Assignees
No one assigned
Labels
Azure.Core Client This issue points to a problem in the data-plane of the library.
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
2 participants
@xirzec @jeremymeng