[Apiman-user] Response when gateway cannot connect to the API implementation

[Eric Wittmann]

+1 good point.  Can you perhaps open a JIRA ticket?  That would be super
helpful and would allow you to automatically track progress on the issue.

-Eric


On Thu, May 4, 2017 at 1:48 PM, Scott Elliott <scottpelliott at gmail.com>
wrote:

> Right now, when the APIMAN gateway cannot connect to the API
> implementation's endpoint, the response code is 500, the message is null,
> and there is a stack trace.  It's not a very useful response for the
> caller, and it's not really an internal problem with the gateway.  It would
> be better if another response code were used (502? 503?) and a useful
> message were returned instead of a stack trace.
>
> _______________________________________________
> Apiman-user mailing list
> Apiman-user at lists.jboss.org
> https://lists.jboss.org/mailman/listinfo/apiman-user
>
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://lists.jboss.org/pipermail/apiman-user/attachments/20170504/c27d43b5/attachment.html