Changing ProxyEndpoint name causes messaging.adaptors.http.flow.ApplicationNotFound error

[#1]

My API Proxy was working just fine using the default ProxyEndpoint name of `default`, but as soon as I changed the name to a different value, I started getting the following error response:

{
    "fault": {
        "faultstring": "Unable to identify proxy for host: secure and url: [myurl]", 
        "detail": { 
            "errorcode": "messaging.adaptors.http.flow.ApplicationNotFound"
        }
    }
}

The ProxyEndpoint name seems to have been updated automatically in all of the other proxy bundle files by the Apigee editor, so I can't understand why this is happening.

[DChiesa]

I don't know exactly what might be the problem, but I have some suggestions.

The error message indicates that Apigee Edge does not have an API proxy deployed to the virtual host ("secure") and basepath ("url") listed there.

Are you sure that when you changed the name of the endpoint, you undeployed and re-deployed the proxy?

Can you verify same with something like

curl -i -n $mgmtserver/v1/o/$org/apis/$proxyname/deployments

[#3]

So interestingly, I fixed the problem by correcting the `<Basepaths>` value inside the main `<APIProxy>` tag; the value I had didn't match the actual base path for the API proxy. What's weird is that when the `<ProxyEndpoint>` name was set to "default", this incorrect `<Basepaths>` value wasn't a problem.