OCI API Gateway Not Forwarding Headers to Backend - Unexpected 401 Unauthorized Response
Can someone help me understand Can someone help me understand I'm experiencing an scenario with the OCI API Gateway where it does not seem to forward the authentication headers to my backend service. After setting up the API Gateway to route requests to a Node.js application running on an OCI Compute instance, I'm getting a `401 Unauthorized` response from the backend even when I'm including the correct `Authorization` header in the request. Here’s a simplified version of how I set up the API Gateway: - API Gateway version: 2.1.0 - The backend target URL is configured correctly, and I've verified that the Node.js application works when accessed directly. This is part of my API Gateway configuration: ```json { "api": { "name": "MyAPI", "protocol": "HTTP", "routes": [ { "path": "/myendpoint", "methods": ["GET"], "backend": { "url": "http://my-node-app-url/myendpoint", "headers": { "Authorization": "{request.header.Authorization}" } } } ] } } ``` I've also enabled CORS on the API Gateway, but I suspect the scenario is that the headers are not being forwarded. To test this, I added some logging in my Node.js application to log the incoming headers, and it doesn't include the `Authorization` header at all. I've tried using tools like Postman and curl to send the request directly to the API Gateway, ensuring that the `Authorization` header is present, but I still receive the `401` behavior. Additionally, I've checked the OCI IAM policies to confirm that the API Gateway has the necessary permissions to invoke the backend service. Is there a known scenario with OCI API Gateway not forwarding headers properly, or is there something I might have missed in the configuration? Any suggestions on how to troubleshoot this further would be greatly appreciated. Any feedback is welcome! My development environment is macOS. How would you solve this?