[reSIProcate] ClientRegistation::onRequestRetry not being called if Retry-After header present

[Scott Godin]

Yes - I agree that these should be made more consistent.  I'll track this as
a TODO item.  Thanks.
Scott

On Fri, Oct 2, 2009 at 6:36 PM, <aron_rosenberg at logitech.com> wrote:

> In DUM, there seems to be inconsistent handling with onRequestRetry and 4XX
> and 5XX errors that have a Retry-After header
>
> ClientRegistration:
> onRequestRetry called only for 408 errors.
> Calls onFailure for all others and then checks
> getDefaultRegistrationRetryTime and Retry-After (but no onRequestRetry is
> fired if Retry-After header is present)
>
> whereas in ClientPublication and ClientSubscription:
> onRequestRetry called for 408 or various 4XX and 5XX responses with a
> Retry-After header
> if -1 returned then from onRequestRetry, then onFailure called
>
> -Aron
>
> Aron Rosenberg
> Sr. Director, Engineering
> Phone: +1 (510) 665-2920
> Logitech Inc, (SightSpeed Group)
>
> _______________________________________________
> resiprocate-devel mailing list
> resiprocate-devel at resiprocate.org
> https://list.resiprocate.org/mailman/listinfo/resiprocate-devel
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://list.resiprocate.org/pipermail/resiprocate-devel/attachments/20091012/a1cadbec/attachment.htm>