May 15, 2020
There is no way to avoid the “//” when posting to a topic in the VANTIQ REST API. The leading slash is part of the “resource id” for the topic – without it VANTIQ will not route the request properly (hence the VANTIQ equivalent of a 404).
What you can do is create a procedure to do the publish and invoke that through the REST API.
Viewing 2 posts - 1 through 2 (of 2 total)
- You must be logged in to reply to this topic.
The problem has been seen in two situations:
1. With an API gateway that does not like the double // in the URI.
2. In the NGINX proxy. NGINX modified “//” to “/”
For example
https://dev.vantiq.com/api/v1/resources/topics/mytopic fails
[
{
“code”: “io.vantiq.resource.not.found”,
“message”: “The requested instance of the topics resource could not be found.”,
“params”: [“topics”]
}
]
https://dev.vantiq.com/api/v1/resources/topics//mytopic succeeds