2 results found
-
Automatic Decompression for GZIP and DEFLATE Content-Encoding in REST Connector
Currently, when using the REST connector, if a stream is gzip or deflate compressed, the data received is successful with a StatusCode of 200, but the body content is garbled due to the Content-Encoding being gzip'd at the source. This requires additional manual effort in transforming the data to be usable.
3 votesWe are happy to let you know that development has begun on your requested feature in Flow Connect.
GZIP support is already available for testing; we missed Deflate, but we'll look into it soon.
-
Feature to log REST calls
It would be nice if we could log somehow if an enduser run a workflow and during a REST call an error occurs, then later a developer could check these log files. Or if the issue is not reproducable in DEV environment, only in PROD/TEST env. (like a similar functionality in Flow Classic).
A use-case from partner:
"If the user experience problems occasionally and we can’t recreate it in the debug.
Another example, sometimes when I get long responetimes during testing I cannot see if that is because of M3 or not. Next time I run it it is quick…2 votesWe are happy to inform you that development work has begun on the telemtry feature which will allow for such logs. Our product team has assigned resources and is actively working on implementing it. We will keep you updated on its progress.
- Don't see your idea?