# Any way to get raw KV data in 1.16 version

**URL:** <https://discuss.hashicorp.com/t/any-way-to-get-raw-kv-data-in-1-16-version/66789>\
**Category:** Consul\
**Created:** [May 8, 2024, 3:37am UTC](https://discuss.hashicorp.com/t/any-way-to-get-raw-kv-data-in-1-16-version/66789 "2024-05-08T03:37:42Z")\
**Posts on this page:** 1\
**Page:** 1

<div class="post-metadata">

**Author:** ![rammohanganap](https://sea2.discourse-cdn.com/hashicorp/user_avatar/discuss.hashicorp.com/rammohanganap/32/35490_2.png) [@rammohanganap](https://discuss.hashicorp.com/u/rammohanganap)\
**Post date:** [May 8, 2024, 3:37am UTC](https://discuss.hashicorp.com/t/any-way-to-get-raw-kv-data-in-1-16-version/66789/1 "2024-05-08T03:37:42Z")

</div>

Hi, I have recently updated consul from 1.8 to 1.16 and i see some behavior change in the KV get raw data http api. While searching i found this:[HCSEC-2021-07 - Consul API KV Endpoint Vulnerable to Cross-Site Scripting](https://discuss.hashicorp.com/t/hcsec-2021-07-consul-api-kv-endpoint-vulnerable-to-cross-site-scripting/23368), so is there a way to preserve the old behavior? i know it is security risk but some of the clients are using that api and breaking the stuff. until we fix all the clients wanted to see if is there a option to preserve the old behavior on fetching raw value on KV data.
