Join GitHub today
GitHub is home to over 28 million developers working together to host and review code, manage projects, and build software together.Sign up
Table of Contents
Cookies may cause slight issues for site administrators using Amber. When Amber stores the content of linked websites, it also stores the cookies at these websites.
Each time a user on the site accesses the stored version of a linked site instead of the live version, the linked site's cookies will be created but will be instead registered to the linking - instead of the linked - site. Browsers set limits on how many cookies can be registered to a single site, so should the user access large numbers (around 70+) of stored websites with cookies, the web browser may prohibit users from accessing any more stored sites. While this limitation is highly unlikely to affect t the site's visitors, the site administrator may encounter this issue when checking the cache quality of various sites.
To solve this issue, you can delete the cookies your web browser has stored for your site. If you are unsure how to do delete cookies within your web browser for a particular site, we recommend the following short guides:
- Chrome: https://support.google.com/chrome/answer/95647?hl=en
- Firefox: https://support.mozilla.org/en-US/kb/delete-cookies-remove-info-websites-stored#w_delete-cookies-for-a-single-site
- Safari: http://support.apple.com/kb/ph11920
- Internet Explorer: http://windows.microsoft.com/en-us/internet-explorer/delete-manage-cookies#ie=ie-11
Attempting to snapshot popular sites like facebook.com or paypal.com may trigger automatic phishing alerts from the visitor's browser. This occurs because browsers have been configured to automatically detect sites mimicking the HTML of high-profile sites, so Amber's snapshots of these sites may trigger warnings.
Depending on how the site administrator has configured Amber, this may not affect visitors to your site. If snapshots are only served to the user when the original site is labeled as "Down," then the snapshots of Facebook or Paypal are unlikely to be accessible by the visitor, since these sites are rarely (if ever) down for long enough to be recorded as such.
However, if the site administrator does wish to make snapshots of linked sites available at all times (regardless of site status), then a user attempting to access a snapshot and seeing a phishing warning may be confused. One way to avoid this issue would be to blacklist sites such as Facebook and Paypal from snapshot, as snapshotting such sites is likely unnecessary (due to near-constant availability).
Amber does not moderate which sites are snapshotted. The site administrator should take caution to ensure that sites that would pose security threats to online visitors (for example phishing sites or download links to malware) are never linked to. We recommend that the site administrator should be just as vigilant in monitoring not only which sites are linked to via your website but also which sites are snapshotted by Amber.
To prevent cross-site scripting (XSS) attacks, the Amber plugin for WordPress serves all cached content to visitors through a sandboxed iframe.
Amber does not snapshot content that appears behind a login. For example, Amber will not snapshot a link to content in an online forum with members-only access. In effect, any content that requires an additional step for access—whether it be logging in, or clicking a link somewhere else—will not be snapshotted properly by Amber.
Amber is only compatible with PHP 5.3 and higher. If your WordPress install is running an older version of PHP, Amber will fail upon install.
At this time, we are only able to support the current version of languages. However, we plan to release an update which will allow Amber to work on WordPress installs which run some older versions of PHP.