Kong: the default upstream timeouts are 60 seconds each

connect, send and read timeouts all default to 60000ms. A hung upstream therefore holds a Kong worker connection for a full minute, and under any real traffic the gateway runs out of connections before the upstream is declared unhealthy.

• Kong: a custom plugin's shared state is per worker, not per node
• Kong: CORS is a plugin, and letting the upstream also send the headers breaks it
• Kong: DB-less mode has no Admin API writes, by design
• Kong: a consumer-scoped plugin only runs after an auth plugin identified the consumer
• Kong: passive health checks never bring a target back
• Kong: strip_path decides what path the upstream actually receives

---

Run this yourself in the Online Java Compiler, spin up a live REST API in the API Sandbox, or practise with Java interview questions.

Published 2026-08-25

© Java Coding Hub · About · Contact · Privacy · Terms