# Staged rollout of Boundary Node security upgrades that might impact dApps - action may be required

**URL:** <https://forum.dfinity.org/t/staged-rollout-of-boundary-node-security-upgrades-that-might-impact-dapps-action-may-be-required/20903>\
**Category:** Developers\
**Created:** [June 22, 2023, 4:23pm UTC](https://forum.dfinity.org/t/staged-rollout-of-boundary-node-security-upgrades-that-might-impact-dapps-action-may-be-required/20903 "2023-06-22T16:23:32Z")\
**Posts on this page:** 1\
**Page:** 3

<div class="post-metadata">

**Author:** ![TusharGuptaMm](https://sea1.discourse-cdn.com/flex023/user_avatar/forum.dfinity.org/tusharguptamm/32/11944_2.png) [@TusharGuptaMm](https://forum.dfinity.org/u/TusharGuptaMm)\
**Post date:** [August 7, 2023, 12:31pm UTC](https://forum.dfinity.org/t/staged-rollout-of-boundary-node-security-upgrades-that-might-impact-dapps-action-may-be-required/20903/41 "2023-08-07T12:31:19Z")

</div>

@skilesare same with us and used same fix

> [@Making HTTP calls from mobile apps](https://forum.dfinity.org/t/making-http-calls-from-mobile-apps/5192/43):
>
> @raymondk, I identified the source of the problem as my oversight in overlooking the boundary security upgrade documentation. Following the recommendation, we made changes to the main base-domain in the request URL, but unintentionally left the canister id in the subdomain, which caused the request to be redirected incorrectly. The original problematic URL was: https://\<canister\_id\>.ic0.app/api/v2/canister//query However, we successfully resolved the issue by using the correct URL: [https://i…](https://ic0.app/api/v2/canister/)

[Previous page](https://forum.dfinity.org/t/staged-rollout-of-boundary-node-security-upgrades-that-might-impact-dapps-action-may-be-required/20903.md?page=2)
