infact it's more bizarre. refreshing the page results in the duplicates sometimes appearing and sometimes disappearing from the

writeDump

unless you can repro the same result on another request to another url / provider, this seems like it would be specific to the feed you're using. we make thousands of http requests to json and xml feeds and if there were a bug in cfhttp that caused data to be duplicated, I think everybody would've run into it

yea it's just bizarre

you could also compare the content-length header of the request against the actual content and make sure they match

I'm just dumping out

reponse.Filecontent

and it's changing

because if the server is saying 'your content is 12000 bytes' and the response is 12000 bytes and contains duplicates, that's the server

of the request or the response?

The response should have a content-length header. All HTTP responses should

no, presuambly in

.Responseheader

what you're seeing may be an artifact of using cfdump. i would suggest just outputting the text file content and verify its length, then refresh a few times and check that it's the same. if it is, then it's just a weirdity with how cfdump works internally (infrequent but i've seen it many times)

Do you mind sharing your cfhttp code? I’m trying to remember the details. We had some weirdness at one point when we weren’t scoping the return value. e.g.

result = 'local.result'

instead of

result = 'result'

.

fwiw, I find hyper (no codlbox required) to be super helpful with stuff like this, a lot easier to debug requests & responses in addition to making repeat, similar requests easy to manage

This could very well be the answer @danmurphy

I’ve not caught the vision of hyper yet. We do a fair amount with cfhttp, but our stuff must be simple enough to not have a huge pull for something more.

Hyper is to cfhttp what qb is to cfquery

Right. Which is overkill at times, for me (qb instead of just queryExecute).

cfhttp(method="GET", charset="utf-8", url="#api_url#", result="result", timeout=8);

            str_result = result.Filecontent;

code is simply the above. and dumping

str_result

. but 'result' is not scoped. So I'm curious as to whether dan's suggestion resolves the issue

If your xml response is long try writing it out to the console or browser instead of using cfdump. There are display limitations by design for that tag.