Running a single BIMserver on a host, but running another single BIMserver on the same host later on, but on a different address (for example a changed context path).
The cookies stored tend to cause problems. There are 2 cookies "address" and "autologin". Both are prefixed with the port already, but not with anything else. The actual location of the cookie seems to always be on the root path.
Changing the root path that is being used to the root path of the client application (BIMvie.ws) might fix this. Could actuallt be a BimServerJavaScriptApi problem.
When people are either:
The cookies stored tend to cause problems. There are 2 cookies "address" and "autologin". Both are prefixed with the port already, but not with anything else. The actual location of the cookie seems to always be on the root path.
Changing the root path that is being used to the root path of the client application (BIMvie.ws) might fix this. Could actuallt be a BimServerJavaScriptApi problem.