If you are creating the Request URL dynamically, it would be helpful to have the computed URL as one of the attributes in the Output and Rejected ports… particularly the latter port so that you can include it in any error messages you may construct.
Archived
HTTPCaller - Add the Request URL as an attribute to the Output and Rejected ports
+31- Influencer
I’d suggest using an AttributeCreator before your HTTPCaller to generate a _URL attribute. You can then reference it in the HTTPCaller and retrieve it afterward.
I wouldn’t want this to be the default behavior of the transformer, because in that case the HTTPCaller would also need to output the request headers, the body, and possibly even authentication details… and I’m not really on board with that, haha.
+8- Safer
I understand the need for debugging but I’d definitely suggest
Maybe it highlights a need for a better way to let users see values of attributes / parameters calculated inside transformers but having them exposed on an attribute probably isn’t the best behavior.