I use the edge HTTP web server to serve a REST API for several microservices. I’ve found handling incoming requests to these services is cumbersome with the current implementation of the HTTP trigger node. I have a few ways we could probably make that better:
Filterable HTTP trigger node…allow filtering on the HTTP trigger node by method & path…or maybe even as a series of expressions. Ensure for path filtering we have glob / regex pattern handling (ie accept everything on path “/requests”, including “/requests/foo” and “/requests/bar”).
If this has to be handled outside the HTTP trigger node, then I’d recommend including complex statements and glob/regex pattern matching in the Switch node. Same use case. This would save me from needing to stack multiple conditionals and switch nodes just to route an incoming request. Right now in order to deal with path routing where I’m using namespaces I’m having to do a string node with a split or something similar. This also works for getting things like deviceIds out of paths for GET/PATCH etc. But would be nice if it were more elegant.
Would love to hear any other thoughts or suggestions!