When using relative URLs, you can specify a base URL path. This base URL is not used in publishing, but allows you to preview your relative links to verify that the address is valid.
You specify a base URL path using the Browse button for the Base URL for Previewing Relative Hyperlinks setting on the General page in the Content Defaults category in the Options dialog box. A base URL path must begin with "http://" or "https://". You can type the address or copy and paste it from another location, such as your browser. If the content is deployed on a locally shared web folder or on an accessible server, you can use the Go button to preview and verify the location. The base path should point to a target directory, but can also point to a filename.
When you preview a relative link in the content, the Developer combines the base URL (in the Options dialog box) with the Relative URL (as specified in the link) to create the path that the system uses to find the target URL. If you change the base URL path, preview automatically uses the new setting for newly created AND existing relative URL links. If you enter a relative URL with no base URL specified, you are notified that a base address for the relative URL is not set.
The base URL path applies to the entire Library and is included in the exported content defaults, so it can be shared with other authors. If different authors use different base URLs, all the relative links may not work. However, if you are using multiple Libraries, each Library can have its own base path.
In published content, the system resolves relative links by combining the relative paths with the current location of the Player's index.html file, which it considers the base URL path. However, the resolved links are tagged as relative links and can be updated in post-publishing. Once the target URL content is deployed on its final server, you can modify the baseUrl variable in the config.js file in the published Player content and enter this address.