2999691eea
This change enables CORS support in the archive — to allow web developers to create web applications with frontend JavaScript code that can fetch pages from the archive (for example, for scraping content from chat logs). Otherwise, without this change, web developers can’t create web apps with frontend JavaScript that can fetch chat logs from the archive and then consume the content of the logs. It’s imaginable that web developers may find use cases for consuming the chat logs in the archive from frontend JavaScript code — at the simplest level, web apps that fetch and scrape logs to get data out of them or to pull out particular snippets from the logs. Developers can anyway already scrape the contents of the archive — by using server-side programming languages or by using `curl` or whatever from the command line. They just can’t do the same from frontend JavaScript code, unless CORS support is enabled. |
||
|---|---|---|
| .. | ||
| client-side-room-alias-hash-redirect-route.js | ||
| content-security-policy-middleware.js | ||
| install-routes.js | ||
| prevent-clickjacking-middleware.js | ||
| redirect-to-correct-archive-url-if-bad-sigil-middleware.js | ||
| room-directory-routes.js | ||
| room-routes.js | ||
| timeout-middleware.js | ||