Search the API Reference:
Acre Web Entrypoints
In order to keep hosted applications securely isolated not only on the server, but from cross-site scripting attacks, each application is given its own domain name. This domain name is composed first by taking the version of the application (which by default doesn't exist so it might not be there at times), the ID of the application, the app owner's Freebase user name and the hosting domain name.
Anatomy of an Acre URL
Special Acre URLs
Some path inside the app URL space have special default meaning in Acre:
- index -- Served if just the host name is requested (with no file).
The following files all have default versions that can be over-ridden just by creating a file of the same name in your app:
- error -- served whenever there is an error, the error info is available in acre.error.
- not_found -- served whenever a file is requested that doesn't exist.
- favicon.ico
- robots.txt
The /acre/ path is reserved for services available in any app:
- /acre/account -- For signing users in and out of an OAuth-enabled app. Must append either /signin or /signout (with an optional ?onsucceed=url)
- /acre/touch -- invalidates the mwLastWriteTime cookie, used by Freebase's caching proxies to know if content is stale (should result in getting the most up to date data)
- /acre/status -- simple health check for the acre server
- /acre/version -- specifies the version numbers for all freebase components
In addition, there is a reserved acre.* in string argument namespace:
- ?acre.console=1 -- shows the log messages (from acre.console) for the current URL
Short App URLs
It is possible to address your Acre app with a shorter URL by claiming a [name].freebaseapps.com domain via the 'versions' tab of the app dialog (that you can reach by clicking on the app name at the top of the app editor).
