Hello all,
Today I fell into a rabbit hole with the HTTP request action in Automations (2024.1).
As the Action lacks the parameters key-value interfacing of a fully fledged HTTPCaller, I needed to build-up the parameter-part of the URL in the text-editor.
There, some URL encoding happens. Spaces are substituted by %20 at least. But I was unable to parse a GeoJSON as the [ ] were not encoded. When I manually url-encoded the parameter values, the encoding (%) was encoded(%25) , so I still did not get a valid GeoJSON from a manual-trigger-Geometry parameter to a parameter in a workspace REST-webhook.
I remember around 2016, the default server.xml in a FME Server installation did allow for non-encoded brackets through an exception in the <connector>. That has long gone in the standard install. Using Kubernetes, even if I wanted to, I would not know how to put that back.
So:
- Has anyone figured-out the encoding which does occur (which and when)?
- @Safe: Could we please have reliable full encoding (including the e ]) so FME Flow eats its own dogfood?
- @Safe: Perhaps bring the parameters-matrix to the Automation HTTP request. This clearly distinguishes between parts of the URL and values which need URL-encoding
- @Safe: A little off-topic, but at least as important, bring the Headers-matrix from the HTTPCaller to the Automation HTTP request. Now I can only set only the Accept header, but not e.g. the Authorization : fmetoken token=1eedda2c5776…...
Kind regards,
Martin
edits: Hey, non-native English speaker….
