ThingSpeak error responses broken?

Hello.

Since a week or two i get strange results from ThingSpeak when there should be an error response.

I an developing a little application with ESP32 and Arduino that logs the state of my garage doors.

Now, while testing my error handling code, i get strange results when there sould be an error response.

The library always states error ERR_BAD_RESPONSE (-303) when there should be some kind of error.

Diving deeper, i recognized that the header field "Content-Length" is missing. Even more, there is always status-code 200 present, only the content is a '0' instead of the number of the datapoint.

Here is what i get when there sould be a rate-limit error:

HTTP/1.1 200 OK
Date: Sat, 09 May 2020 15:59:52 GMT
Content-Type: text/html; charset=utf-8
Transfer-Encoding: chunked
Connection: keep-alive
Status: 200 OK
ETag: W/"5feceb66ffc86f38d952786c6d696c79"
Cache-Control: max-age=0, private, must-revalidate
Set-Cookie: request_method=POST; path=/
X-Request-Id: 08ee2445-a77c-400c-aa80-40d6ef365aa4
X-Runtime: 0.016066
X-Powered-By: Phusion Passenger 4.0.57
Server: nginx/1.9.3 + Phusion Passenger 4.0.57

That is what i get for a wrong Write-API Key:

HTTP/1.1 400 Bad Request
Date: Sat, 09 May 2020 16:04:47 GMT
Content-Type: text/html; charset=utf-8
Transfer-Encoding: chunked
Connection: keep-alive
Status: 400 Bad Request
Cache-Control: no-cache
Set-Cookie: request_method=POST; path=/
X-Request-Id: 0efeb3d6-75b7-4e4a-862a-db3b2925888d
X-Runtime: 0.002920
X-Powered-By: Phusion Passenger 4.0.57
Server: nginx/1.9.3 + Phusion Passenger 4.0.57

Here, content-length is also missing. But the status code is right.

This is what i get for a good transaction:

HTTP/1.1 200 OK
Date: Sat, 09 May 2020 16:05:49 GMT
Content-Type: text/html; charset=utf-8
Content-Length: 4
Connection: keep-alive
Status: 200 OK
ETag: W/"33bf4329c846019957cdba15fd5767df"
Cache-Control: max-age=0, private, must-revalidate
Set-Cookie: request_method=POST; path=/
X-Request-Id: 257d7f8f-bd66-4846-acf6-95b4af464b92
X-Runtime: 0.036851
X-Powered-By: Phusion Passenger 4.0.57
Server: nginx/1.9.3 + Phusion Passenger 4.0.57

This seems all right.

I think this must be a server error. Have there been any changes in the last weeks? Another application i developed some time ago behaved correct and now shows also the -303 error sometimes.

Answer 1

[Vinod]

We are looking into this. I'll post a response here when we have more information.