Daniel (dB.) Doubrovkine

> The middleware is an interesting idea. Are you thinking it would store them on the instance of the client? Yep.

> I'm taking a crack at the middleware approach now. Do you think it should be optional via a new web config setting/attribute? Only if it creates significant overhead. Without...

Ugh. Sounds familiar. So we continue maintaining a community https://github.com/slack-ruby/slack-api-ref that can be kept up-to-date as needed by the consumers.

It's just an HTTP POST to that URL, no? Examine the error in the 500, you're probably not formatting the message right. Try to build a very simple sample on...

What's `connection` in this case? I totally think that making it easier would be great for the library. Can you post a little bit more code around the above and...

This is not in a realtime context, right? I mean the response URL appears as a response to what code? I think that response needs to become a class that...

Oh I see, this is in response to a command, something that I had to do in https://github.com/dblock/slack-market/blob/master/slack-market/api/endpoints/slack_endpoint.rb for example. I guess there's nothing to do in the client indeed....

No decision @avand, see my suggestion if you want to try to PR something.

The connection is setup [here](https://github.com/slack-ruby/slack-ruby-client/blob/018dcfdea5a4bfb63310ac16e0dfceb1827816f4/lib/slack/web/faraday/connection.rb#L7) for the web client. It's private. We don't seem to expose arbitrary headers or a connection editing mechanism. Try `client.send(:connection).headers['X-Slack-No-Retry'] = 1` as a workaround?...

For the specific `X-Slack-Retry-Reason` error I would also appreciate a custom exception like we do for rate limiting.