If cms and site run on same host, and renderingHost has been set on the HttpSession, then even when the site is loaded outside the cms, the contextPath is included in the URL

Not sure if there is a work around for this. Problem is:

1) In HstFilter we have
String renderingHost = HstRequestUtils.getRenderingHost(containerRequest);
if (renderingHost != null) {
requestContext.setRenderHost(renderingHost);

2) In HstContainerURLProviderImpl#toURLString we have:

else if (requestContext.getRenderHost() != null || requestContext.getResolvedMount().getMount().isContextPathInUrl())

{ urlBuilder.append(containerURL.getContextPath()); }

However, if cms and site run on same host, I doubt whether we can fix this: At the same time, it most likely won't be an issue in general.

Needs some more thinking and see if in practice we get issues with it