The [n/o]c_sciencemesh app could ping a method on Reva's ocm module to see if it's reachable.
Also, Reva's rhttp and ocmd routers could have better error logging about the meaning of 'head' and 'tail', for instance also report what the expected value was, e.g.
head was "", instead of "ocm", "ocdav", ...
head was "ocm", instead of "invites", ...
Maybe even check if the URL contains "invites" in the wrong position, suggest an ocm prefix to make it correct
The [n/o]c_sciencemesh app could ping a method on Reva's ocm module to see if it's reachable. Also, Reva's rhttp and ocmd routers could have better error logging about the meaning of 'head' and 'tail', for instance also report what the expected value was, e.g.
head was "", instead of "ocm", "ocdav", ...head was "ocm", instead of "invites", ...Maybe even check if the URL contains "invites" in the wrong position, suggest an ocm prefix to make it correct