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 …

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!

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

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

Bug reports

Olav May 22, 2025, 7:18pm 4

Hello! This bug has been fixed in version 117.

Topic		Replies	Views
Release Notes 119 Release notifications	0	82	July 3, 2025
Web Request - Issue with url-encoded Ask the community	5	119	October 22, 2024
Web Request failed: TypeError: source.no is not a function Bug reports	10	109	February 2, 2026
Previously working request parser function now fails with "FunctionEvalError: Invalid character" Bug reports web-request	12	516	May 27, 2024
Problem On View Value Bug reports	1	193	November 29, 2023

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

Related topics