Nested Http Route in Azure Function returns 404 not found - node.js

Question

I have multiple functions handling GET, PUT & POST API's with different paths in my Azure Function and they all work fine. Each function has one index.js file handling one HttpMethod only & I have a routePrefix of "api" in the hosts.json. The function.json for one of the functions can be found below
{
"bindings": [
{
"authLevel": "anonymous",
"type": "httpTrigger",
"direction": "in",
"name": "req",
"route": "bike/{id}/like",
"methods": [
"put"
]
},
{
"type": "http",
"direction": "out",
"name": "res"
}
]
}
The problem I am facing is the two PUT requests below don't work & I get a 404 not found. However this seems to work when I run the function locally in vscode & check using Postman.
http://<MyAzureFuncName>.azurewebsites.net/api/bike/63d51c0bb593aec8734638e5/like
http://<MyAzureFuncName>.azurewebsites.net/api/bike/63d51c0bb593aec8734638e5/dislike
UPDATE 1
I have just found out that calling the above API's using the test/run feature on the Azure function in the portal works but not when I try using Postman. Any ideas why this is the case
I also have GET & an update method for PUT following a similar signature (shown below) which both work locally but on Azure the PUT is returning the GET result when checking with Postman. Could this PUT overload be the cause for the mix up.
http://<MyAzureFuncName>.azurewebsites.net/api/bike/63d51c0bb593aec8734638e5
UPDATE 2
I have found that all the above PUT requests work if I use https instead of http. The other POST, DELETE & GET requests work with both. This is all the more baffling, can anyone shed some light on this.
I would appreciate any help & guidance in spotting the obvious.
UPDATE 3
I do not have the TLS/SSL settings (classic) option in the Settings for my function app or in any of my app services for that matter. I am assuming this was something on the old portal.
Thanks

Answer 1

Since you are able to reach the endpoint with https and not with http, I assume that the error is the HTTP Only setting.
Navigate to your Function App, and go to TLS/SSL settings (classic) in the Settings section and switch HTTPS Only to Off.
When it comes to this section:
I also have GET & an update method for PUT following a similar
signature (shown below) which both work locally but on Azure the PUT
is returning the GET result when checking with Postman. Could this PUT
overload be the cause for the mix up.
I would say it's normal to return the resource when making a PUT request. For example, if you update the resource, you would then return the data with the updated information.
Hope it helps.