Due to how RStudio Connect routes requests from Tableau, nested paths are not currently supported. All endpoints must be at the root path of the router.
In order to properly accommodate this limitation, plumbertableau will be updated to only honor the final entry in the script value sent in a Tableau request. For example, if the Tableau request looks like the following:
Then plumbertableau will route the request to /capitalize. This is due to the fact that the above request may reference an API hosted at RStudio Connect at /foo/bar, while the internal API route is /capitalize.
After further discussion and evaluation, we decided to let RStudio Connect handle the path rewriting. This means that nested routers are supported in plumbertableau.
Due to how RStudio Connect routes requests from Tableau, nested paths are not currently supported. All endpoints must be at the root path of the router.
In order to properly accommodate this limitation,
plumbertableau
will be updated to only honor the final entry in thescript
value sent in a Tableau request. For example, if the Tableau request looks like the following:Then
plumbertableau
will route the request to/capitalize
. This is due to the fact that the above request may reference an API hosted at RStudio Connect at/foo/bar
, while the internal API route is/capitalize
.