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

Bug reports
1

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

image

image

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

2

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!

3

Great!

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

1 Like
4

Hello! This bug has been fixed in version 117.