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

Use 'Retry-After' header from responses to wait for results #333

Open
rozele opened this issue Nov 3, 2020 · 0 comments · May be fixed by #347
Open

Use 'Retry-After' header from responses to wait for results #333

rozele opened this issue Nov 3, 2020 · 0 comments · May be fixed by #347

Comments

@rozele
Copy link
Contributor

rozele commented Nov 3, 2020

Currently, the polling duration is hard-coded in the NLU.DevOps tool. If the HTTP services for LUIS, Dialogflow or Lex are returning a 'Retry-After' header, we should respect that.
rozele added a commit to rozele/NLU.DevOps that referenced this issue Nov 23, 2020
@rozele
Leverage "Retry-After" usage to LUIS API calls
fbe450c 
If a "Retry-After" HTTP response header is returned by LUIS, this change ensures that header is respected.

Fixes microsoft#333
@rozele rozele linked a pull request Nov 23, 2020 that will close this issue
Open
rozele added a commit to rozele/NLU.DevOps that referenced this issue Nov 23, 2020
@rozele
Leverage "Retry-After" usage to LUIS API calls
2d3848c 
If a "Retry-After" HTTP response header is returned by LUIS, this change ensures that header is respected.

Fixes microsoft#333
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
None yet
Projects
None yet
Milestone
No milestone
Development

Successfully merging a pull request may close this issue.

Leverage "Retry-After" usage to LUIS API calls rozele/NLU.DevOps
1 participant
@rozele