Following up #45 and #63 issues, the devs might want to return a value in the Retry-After header.
As per the specs on 413 and 503 HTTP codes:
This response should be used for temporary conditions and the Retry-After HTTP header should, if possible, contain the estimated time for the recovery of the service.
To get it done, the implementation should include:
An optional int parameter (to indicate the waiting period) to IDomainResult in methods ContentTooLarge() and CriticalDependencyError().
Handle the field in conversions in DomainResultExtensions and DomainResultExtensions in DomainResults.Mvc project.
This would require breaking changes to IDomainResultBase interface to store the Retry-After, which might add unnecessary complexity which will be consumed just by a handful of devs.
Following up #45 and #63 issues, the devs might want to return a value in the Retry-After header. As per the specs on 413 and 503 HTTP codes:
To get it done, the implementation should include:
intparameter (to indicate the waiting period) toIDomainResultin methodsContentTooLarge()andCriticalDependencyError().DomainResultExtensionsandDomainResultExtensionsinDomainResults.Mvcproject.This would require breaking changes to
IDomainResultBaseinterface to store theRetry-After, which might add unnecessary complexity which will be consumed just by a handful of devs.