Skip to content

FR: Avoid or handle multple HttpIn with same listening URL #5643

@qabi

Description

@qabi

I accidentally ended in a situation where I had two HttpIn nodes listening on the same URL path, in different flows.

It turned out that one was listening from startup (last in flows.json?) and then after making a change to the other node and redeploying it, this second note started receiving the requests. In larger setups with multiple editors, things like this can happen.

I suggest that using the same URL path should be prevented, or alternately the request delivered to all nodes listening on the given path.

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions