Picking up a thread from Linkedin Discussion https://www.linkedin.com/posts/diego-giudici-2a4a82183_apache-camel-exec-component-to-be-used-to-activity-7361417086029520896-rX9S?utm_source=share&utm_medium=member_desktop&rcm=ACoAAAADB-oBkocmID4JNAjX2CC91jH5a8sV5l4
here is route: https://gist.github.com/chiragsanghavi/b83ef5babc6d02b2757ae6a9cd100281 Technically this is not a bug, as site https://swapi-graphql.netlify.app/.netlify/functions/index leads to a direct, which shouldn't happen in real life. GraphGL component initiates request using a POST, but redirect is handled by Apache Common HTTP Client - and as GET - which is where the "query" is not passed to the redirected URL. what will be better way to handle it ? Should such scenario be handled by passing a custom http client that disables redirect and capture error? If GraphQL component was built using camel-http underneath - it could return many more values to make some decisions after exchange is called .
