API Gateway: Route HTTP Assertion with proxy does not work
search cancel

API Gateway: Route HTTP Assertion with proxy does not work


Article ID: 135412


Updated On:


API SECURITY CA API Gateway Precision API Monitoring Module for API Gateway (Layer 7) CA API Gateway Enterprise Service Manager (Layer 7) STARTER PACK-7 CA Microgateway CA API Gateway


If a HTTP route assertion is used in policy with HTTP credentials specified AND a proxy is specified where the proxy does not require a user name and password, the requests will fail with the below error

<l7:detailMessage id="4038">

       Downstream service returned status (503). This is considered a failure case.



API Gateway 9.2


The following cluster-wide property will need to be added

CWP Name: io.httpEnableAutoChallenge 

value: true 

This is a hidden property that is editable by typing in its name in the Key field and then pressing [Tab]. (It cannot be located via the drop-down list.)

This property enables authentication to be handled automatically (HANDLE_AUTHENTICATION) by the underlying HTTP client. More details can be found here from the Apache page -> https://hc.apache.org/httpcomponents-client-ga/httpclient/apidocs/org/apache/http/client/params/ClientPNames.html