Liquid syntax error: 'raw' tag was never closed
For further actions, you may consider blocking this person and/or reporting abuse
Read next
Why Quick Fixes Fail: Rethinking Microservices Testing
Signadot -
Static Keyword in C# Explained in 1 Minute
DotNet Full Stack Dev -
Autofac Dependency Injection in ASP .NET Core 8
DotNet Full Stack Dev -
Downstream Resiliency: The Timeout, Retry, and Circuit-Breaker Patterns
Rafael Câmara -
Top comments (2)
Pretty decent project!
What happens if a host from your configuration is down? Is this case handled already?
In this step, what has returned from the down host is returned, will be returned to the original client. For example if a 500 error occurs or if a bad request happens, all the HTTP status, body and header is exactly repeated to the original client.
But by your good hint, I am inspired to ban the down host temporairly or permanently. So do not send requests to hosts which are down. The definition of
downcan be configurable. For example a timeout error and all 500 family error can be considered down and all other error can be consider repeatable actions.