# New Web Request Path option is too eager when removing forward slashes

**URL:** <https://community.appfarm.io/t/new-web-request-path-option-is-too-eager-when-removing-forward-slashes/1844>\
**Category:** Bug reports\
**Tags:** web-request\
**Created:** [May 13, 2025, 1:32pm UTC](https://community.appfarm.io/t/new-web-request-path-option-is-too-eager-when-removing-forward-slashes/1844 "2025-05-13T13:32:50Z")\
**Posts on this page:** 4\
**Page:** 1

<div class="post-metadata">

**Author:** ![oyvind.byhring](https://dub1.discourse-cdn.com/flex013/user_avatar/community.appfarm.io/oyvind.byhring/32/1060_2.png) [@oyvind.byhring](https://community.appfarm.io/u/oyvind.byhring)\
**Post date:** [May 13, 2025, 1:32pm UTC](https://community.appfarm.io/t/new-web-request-path-option-is-too-eager-when-removing-forward-slashes/1844/1 "2025-05-13T13:32:50Z")

</div>

I’m a big fan of the new way of defining URL’s in web requests since I can just store the base URL of an API as a secret and set the path per-request, but I’m having problems calling an endpoint defined like this: /v1/chat/

It seems like Appfarm tries to fix leading and trailing forward slashes in the Path, as in a different call where I use /health it works with all these variants in Path:

![image](https://europe1.discourse-cdn.com/flex013/uploads/appfarm/original/2X/b/b261487ee3567997493a99b1ca22b7d061de7dfe.png)

![image](https://europe1.discourse-cdn.com/flex013/uploads/appfarm/original/2X/d/d387904d9c27fe5f8f0e743608daaf64465752da.png)

![image](https://europe1.discourse-cdn.com/flex013/uploads/appfarm/original/2X/4/4bf7d04f1c3641b92fd450f783b7bd64bce4f84a.png)

… but I need that / at the end for my chat endpoint 😃

---

<div class="post-metadata">

**Author:** ![emma](https://dub1.discourse-cdn.com/flex013/user_avatar/community.appfarm.io/emma/32/1649_2.png) [@emma](https://community.appfarm.io/u/emma)\
**Post date:** [May 15, 2025, 11:30am UTC](https://community.appfarm.io/t/new-web-request-path-option-is-too-eager-when-removing-forward-slashes/1844/2 "2025-05-15T11:30:35Z")

</div>

Hi!

We have investigated this and it looks like our code is structured in a way that always removes leading slashes. I have now made a challenge on this:) Thank you for letting us know!

---

<div class="post-metadata">

**Author:** ![oyvind.byhring](https://dub1.discourse-cdn.com/flex013/user_avatar/community.appfarm.io/oyvind.byhring/32/1060_2.png) [@oyvind.byhring](https://community.appfarm.io/u/oyvind.byhring)\
**Post date:** [May 15, 2025, 1:34pm UTC](https://community.appfarm.io/t/new-web-request-path-option-is-too-eager-when-removing-forward-slashes/1844/3 "2025-05-15T13:34:30Z")

</div>

Great!

Make sure you also don’t cut off trailing forward slashes. Some endpoint URLs end with a /

---

<div class="post-metadata">

**Author:** ![Olav](https://dub1.discourse-cdn.com/flex013/user_avatar/community.appfarm.io/olav/32/63_2.png) [@Olav](https://community.appfarm.io/u/Olav)\
**Post date:** [May 22, 2025, 7:18pm UTC](https://community.appfarm.io/t/new-web-request-path-option-is-too-eager-when-removing-forward-slashes/1844/4 "2025-05-22T19:18:49Z")

</div>

Hello! This bug has been fixed in [version 117](https://community.appfarm.io/t/release-notes-117/1859).