4.2.3.15.1. HTTP Client OUT Troubleshooting

Troubleshooting a new HTTP client setup is always complex. It can quickly get out of hand however if you don't follow some basic first tips. For example, configure and troubleshoot your calls one at a time as opposed to drawing out a complex setup prior to testing. Identifying the origin of problems can be much more difficult in a large flow.

Configure your gateway to fail fast

By default, in order to account for possible network interruptions, our client out gateways will retry your calls according to a strategy defined in your gateway's properties:

When you're setting up your gateway, you will want to have a retry strategy set at "No retry". That way your test message will directly fail or passe during its one and only execution of your HTTP flow. This will also guarantee that your resubmissions will not overlap with retries of a previous undelivered message. This ought to be changed back to a more production-suited retry strategy once you've finished your setup.

Choosing Your First Call

Your first call does not have to be your real first call. If possible, select the simplest smallest call you have. If you have authentication needs, start with checking your authentication on a very basic call that doesn't require complex data.

Troubleshooting Authorization Headers

If you are computing your HTTP Authorization headers, add the same script/metadata also to an Authorization2 header. Authorization headers are hidden in the zip export for security reasons but when troubleshooting authentication errors, checking that your Authorization header has the expected content can be useful. Make sure to remove this duplicate header later but in the meantime it will allow you to check your values.