Forum Discussion
JeffPeterson1
3 years agoQrew Captain
Maybe pipelines isn't passing that URL field across as a proper JSON object.
Try writing the field in pipelines like this:
{{a.url_for_temp_tablescan|tojson}} and see if that fixes it.
------------------------------
Jeff Peterson
------------------------------
Try writing the field in pipelines like this:
{{a.url_for_temp_tablescan|tojson}} and see if that fixes it.
------------------------------
Jeff Peterson
------------------------------
- EdwardHefter3 years agoQrew CadetNope, that didn't work either. It's frustrating because I can see it passing a URL, but TinyURL's API is saying it isn't getting one....
------------------------------
Edward Hefter
www.Sutubra.com
------------------------------- JeffPeterson13 years agoQrew CaptainTry pointing your pipeline to a requestbin (https://requestbin.com/) or some similar service and trigger it so you can see exactly what pipelines is sending.
------------------------------
Jeff Peterson
------------------------------- EdwardHefter3 years agoQrew CadetSOLVED
It turns out I need to use the header content-type: application/json or else TinyURL's API will give me a "no URL found" error (which doesn't match the problem at all). I was able to track it down using https://apirequest.io/ and sending all sorts of messed up stuff at TinyURL.
Jeff, I don't know if I needed to use the "to_json" filter or not, but it works with it so I am not going to take it out now!
------------------------------
Edward Hefter
www.Sutubra.com
------------------------------