Why do I get a Network Error/Access Denied message when trying to access Timetracker Hubs?
This error has occurred when a user attempts to access any of the TFS Timetracker hubs within the application.
Technically, this results when the browser blocks cross-domain requests (CORS) because of iframe sandboxing or to put it another way, when the target (extension) origin *starts with* the TFS origin, then it is treated as being the same-origin. In this case, TFS being on the default SSL port means the port will be omitted and this defect will result.
Until this defect is fixed by Microsoft, we are recommending the current workaround to assist in alleviating the resulting network error/access denied messaging:
- Create different URL addresses for TFS in the TFS Administration Console and Timetracker in Timetracker Configuration Tool respectively, i.e. webapptfstest for TFS and webapptttest for Timetracker.
- Create non-standard, differing ports for TFS in the TFS Administration Console and Timetracker in the Timetracker Configuration Tool, e.g. 4433 for TFS and 8090 for Timetracker. IMPORTANT: Please make sure that the TFS port number doesn’t start with Timetracker's port number, i.e. TFS: 844 and Timetracker: 8443; this will generate the error.