REST Connector: Configurable redirect handling (follow 3xx redirects) , also applies to HTTP Polling Connector #6421
Description
Is your feature request related to a problem? Please describe.
When using the Camunda 8 REST Connector to call APIs that respond with HTTP redirects (3xx), the connector does not follow the redirect automatically. This differs from common tooling such as Postman, where following redirects is the default behaviour. As a result, calls that succeed in testing can fail or require extra process logic when implemented with the connector.
This also impacts the HTTP Polling Connector, as it is built on top of the REST Connector, so the same redirect behaviour affects polling use cases.
Describe the solution you'd like
Add support for following HTTP redirects (3xx) in the REST Connector, and make it configurable (for example, a “Follow redirects” toggle/setting). Ideally the setting should allow users to enable/disable redirect following, and apply consistently anywhere the REST Connector is used, including the HTTP Polling Connector.
Describe alternatives you've considered
Avoid redirected endpoints by hardcoding the final URL (when possible).
Handle redirects manually by detecting 3xx responses and issuing a second request to the Location header within the process.
Both alternatives add unnecessary complexity and are error-prone.
Additional context
The HTTP Polling Connector is built on top of the REST Connector, so implementing redirect handling at the REST Connector level would likely cover both connectors. Users expect redirect-following behaviour because it is the default in tools like Postman, and many APIs rely on redirects for URL normalisation, moved resources, or edge/front-door routing.