You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@camel.apache.org by "Claus Ibsen (Jira)" <ji...@apache.org> on 2022/09/03 14:50:00 UTC

[jira] [Commented] (CAMEL-18177) camel-slack - Honour Retry-After when requests are rate-limited

    [ https://issues.apache.org/jira/browse/CAMEL-18177?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17599945#comment-17599945 ] 

Claus Ibsen commented on CAMEL-18177:
-------------------------------------

Ah yeah if the consumer is scheduled we could maybe grab that seconds and then store that in some state and then skip the poll if still reminding seconds left - then we can have some kind of method a component  can implement that can support grabbing this rate limit until header

> camel-slack - Honour Retry-After when requests are rate-limited
> ---------------------------------------------------------------
>
>                 Key: CAMEL-18177
>                 URL: https://issues.apache.org/jira/browse/CAMEL-18177
>             Project: Camel
>          Issue Type: Improvement
>          Components: camel-slack
>            Reporter: Luca Burgazzoli
>            Priority: Minor
>             Fix For: 3.x
>
>
> According to slack's doc:
> {code}
> If you exceed a rate limit when using any of our HTTP-based APIs (including Incoming Webhooks), Slack will return a HTTP 429 Too Many Requests error, and a Retry-After HTTP header containing the number of seconds until you can retry.
> {code}
> We should explore if we can honor the  Retry-After seconds to perform the next poll.



--
This message was sent by Atlassian Jira
(v8.20.10#820010)