You can put milton into a servlet context on path /caldav easily
enough, just be sure to set the contextPath property on the builder
so milton knows to ignore that path segment in resource location
You should definitely not do this. Caldav clients use the "well
known" protocol to make connections, and that starts with accessing
a special resource at /.well-known/caldav
Milton provides this resource but milton needs to be mounted on the
root to be able to provide it.
This is something which has been discussed in great detail with many
developers. The simplest thing is to usually use a subdomain like
caldav.mydomain.com. A subdomain is basically the same as a context
path in terms of deployment
On 14/05/16 06:31, PGT wrote:
I am test-driving milton on my application and it looks fine - but I need to depoy the URLS under the /caldav" path.
What ist the best approach do archive this?