This is the second time in few years ThingHTTP changes the way it returns data; any way to roll that back or control it?
Boyan Biandov
on 26 Jul 2022
Latest activity Reply by Christopher Stapels
on 26 Jul 2022
Hi everyone,
This is the second time in few years ThingHTTP changes the way it returns data; any way to roll that back or control it? Back in 2020 it statted padding the GET request with CRs and LFs (last time I forgot what changed but it was similar - just padding the GET return with characters).
Now it's adding "0" zero after the GET payload and then 2 CRs and LFs at the end after that zero;
Is there any way to control how ThingHTTP returns the payload back? It's messing up my parsing firmware :)
3 Comments
Time Descending
is it possible that the change in characters is coming from the host website?
You might also consider using MATLAB code in the ThingSpeak MATLAB analysis app to read and process the webpage, then the result migth be a little more stable.
Sorry, it's ThingHTTP; created a brand new app; using the example scneario; same exact issue:
Unfortunately there arent specifications on the return properties for ThingHTTP. Some of it is determined by third party libraries and the framework software. We often have to change our example scenario for similar reasons. You could use MATLAB analysis to sanitize the response and write it to a channel and then have ThingHTTP provide the sanitized response.
Sign in to participate
