Using the APIcast Authentication Caching Policy to mitigate network connectivity issues in Red Hat 3scale API Management

Solution Verified - Updated -

Issue

In the APIcast error log sometimes messages similar to this appear:

2015/11/20 11:33:51 [error] 3578#0: *1 upstream timed out (110: Connection timed out) while connecting to upstream, client: 127.0.0.1, server: , request: "GET /api/activities.json?user_key=USER_KEY HTTP/1.1", subrequest: "/threescale_authrep", upstream: "https://10.0.0.1:443/transactions/authrep.xml?provider_key=PROVIDER_KEY&service_id=SERVICE_ID&usage[hits]=1&user_key=USER_KEY&log%5Bcode%5D=", host: "localhost"

The code returned to the user is HTTP 403.

Environment

  • Red Hat 3scale API Management
    • SaaS
    • On-premise >=2.2

Subscriber exclusive content

A Red Hat subscription provides unlimited access to our knowledgebase of over 48,000 articles and solutions.

Current Customers and Partners

Log in for full access

Log In