I have a cfhttp call that is running a basic GET request to an API endpoint that simply returns a small data object (struct). If I hit the api endpoint directly in the browser it returns data every time with 200 status and data returned. However, when I try and call the endpoint using cfhttp() I occasionally see an error:

string	key [filecontent] doesn't exist

To try and mitigate this occasional error I run the cfhttp in a while loop and give it up to 4 attempts to call the api. However, I still see the above error more often than should be possible. Is there anything I can do to further mitigate this issue - is there an issue with cfhttp?

@davla Put in some debgging and when filecontent doesn't exist, log out the rest of the cfhttp response. I assume the status code and status text will give you some clues

I occasionally see this as well:

The key [filecontent] does not exist, only the following keys are available: [errordetail].

So I guess I need to output that error detail. The problem is that I can’t replicate the issue consistently to debug. I’ll have to add some extra debugging and then just wait and see.

Yep, you just gotta' add the debuggin, sit back, and wait for it to happen again

True, however it’s also our api and I know it’s responding with a 200 every time - I can see the requests in the logs on the API. I guess cfhttp is choking somewhere after that which I need to get to the bottom of - time to write a test case!

however it’s also our api and I know it’s responding with a 200 every time

If yer calling code can't reach yer API... it's not gonna get a 200OK.