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

HTTP proxying fails at initialization if worker endpoint is not yet ready #9954

Closed
fabiocav opened this issue Mar 27, 2024 · 0 comments · Fixed by #9949
Closed

HTTP proxying fails at initialization if worker endpoint is not yet ready #9954

fabiocav opened this issue Mar 27, 2024 · 0 comments · Fixed by #9949
Assignees
@fabiocav
Labels
area: http Items related to experience improvements for HTTP triggers

Comments

@fabiocav
Copy link
Member

At initialization (specialization or worker launch), when using HTTP proxying, if the worker HTTP endpoint is not fully initialized, the request will never be sent to the worker and there are no logs showing an issue.

The proxying flow should be improved to deal with potential transient failures and ensure any issues are properly logged.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees

@fabiocav fabiocav

Labels
area: http Items related to experience improvements for HTTP triggers
Projects
None yet
Milestone
No milestone
Development

Successfully merging a pull request may close this issue.

Fixing issues with HTTP request forwarding and adding retries Azure/azure-functions-host
1 participant
@fabiocav