I used the proxy-middleware package to rewrite the path of the actual API URL in the Nodejs file to /api/events/restservices/api/disaster/v1/events > in order to hide the actual url , instead of using lgw with a different environment to call the api, we use the CDP GRM edge URL to make the call, just like we call actual- instead of .
Problem - When deployed, a Pod responds with data from its request URL - "grm-edge-url/api/events", where grm-edge-url has podnumber:portnumber; and it fails with a response of 400 bad request, the body response is "Unrecognized configuration" and its request URL - similar to other requests with a different podnumber:portnumber. actual lgw/api/events grm-url/api/ events
Testing in postman - real URL and grm edge URL - gives response but another pod gives 400 error.
![[Web front-end] Node.js quick start](https://img.php.cn/upload/course/000/000/067/662b5d34ba7c0227.png)
If you encounter a 400 error in a Kubernetes Pod with the response "Unrecognized Configuration", here are some steps you can take to resolve the issue:
Double check the API configuration for any errors or missing parameters. Use kubectl logs to view the logs of the problematic pod to gather more information. Check the API server logs for any relevant error messages or misconfigurations. Verify network connectivity and ensure there are no DNS or firewall issues. Compare the configuration of the problematic Pod to other Pods in the same deployment. Try updating or restarting the pod to resolve any inconsistencies. Please see the API documentation or support for specific troubleshooting steps. If you need more specific help, please provide additional details.