As of 10-4-2021 the option of &headers=false stopped working?
Hi everyone,
I need your help. As of 10-4-2021 the option of &headers=false stopped working?
It worked beautifully for about 2 years (circa early 2020) and suddenly on 10-4 the headers are being returned despite this option in the URL (no testing with Chrome isn't a credible test, it internally suppresses them regardless)
Need your help, if there's a way to suppress headers and just return the value of interest as it worked prior to Monday 10-4-2021
Thank you Boyan
3 Comments
Time Descending
There was no release near 10-4-2021. I think it works fine though. I just tested in Postman. with headers=true, I get 16 headers Data, Content-type, Content-Length, Connection, Status, X-Frame-Options, Access-control-allow-Origin, Access-Control-Allow-Methods, Access-Control-Allow-Headers, Access-Control-Allow-Age, ETag, Cahce-Control, x-Request-Id, X-Runtime, X-Powered-By and Server. with headers = false, I get 11 headers: Data, Content-type, Content-Length, Connection, Status, ETag, Cahce-Control, x-Request-Id, X-Runtime, X-Powered-By and server.
Thanks Chris, that's the catch, before 10-4 with headers = false I was receiving exactly zero headers, literally what was returned was the the string of interest. Now I get these 11 headers and that's the issue for me. Thanks
What is the URL your thingHTTP is hitting? Perhaps that website changed and is now including headers?
ThingSpeak's last update at the time of this writing was in mid September 2021 so this could not have been a change on our end.
