[Bug]: Timeseries Recent call forces conflicting formats on call

[NobuNobuu]

Describe the bug

So when you load up a timeseries recent call as say a json, and you can see in the network tab that it calls for a json, for some reason xml gets forced into the call too causing the formats to conflict and error out. Got some examples from dev and prod
https://water.dev.cwbi.us/cwms-data/timeseries/recent?office=SWF&ts-ids=LBWT2.Elev.Inst.1Hour.0.Decodes-Rev&_cb=1785860195842

https://cwms-data.usace.army.mil/cwms-data/timeseries/recent?office=SWF&ts-ids=LBWT2.Elev.Inst.1Hour.0.Decodes-Rev

Expected behavior

I'm expecting just a [] from this timeseries as it's empty right now.

To Reproduce

In swagger when you use timeseries recent, put in office and timeseries, then grab the request url it gives and check it out.

Priority

Medium

Logs/Incident Identifier

{"message":"Formatting error:No Format for this content-type and data type : (application/xml, cwms.cda.data.dto.RecentValue)","incidentIdentifier":"3dc7bf58-d804-41bd-bfbc-357badb6ae1e","source":"Parser","details":{}}

CURL Commands

CDA Version

2026.07.31-develop and 2026.05.12-f

Additional context

No response

[MikeNeilson]

Thanks, just confirmed the code isn't processing the header correctly to return the expect application/json.