URL Handling

When fetching remote files from your HTTP server, Emcee expects to fetch ZIP archives. Emcee allows you to specify what file you are referring to inside ZIP archive via URL fragments.

For example, the following URL means fetch ZIP from http://example.com/archive.zip, extract it and use the file MyApp.app under apps folder.

http://example.com/archive.zip#apps/MyApp.app

You can also include any HTTP header values by using JSON. This can be used for authentication, tracking, or any other purposes.

{"url": "http://example.com/archive.zip#apps/MyApp.app", "headers": {"h1": "v1"}}

WARNING: Emcee uses URL as a key to cache URL contents locally. E.g. build artifacts and runtime dump results are cached, and URL is a cache key. It is important to understand that changing contents of URLs remotely may not be respected by Emcee if it already has a local copy of the file in its cache.