Change Details

Steps to Reproduce 1) Create a new blog entry at https://phabricator.wikimedia.org/phame 2) Browse to the new blog entry Actual Results Blog page is served directly from Phabricator. Blog entry URLs are ugly. Requested Results Page is served from Wikimedia CDN cache if possible. Blog URLs are prettier. Brandon suggested that, with the creation of a specific URL (subdomain?) particular to Phame, it would be much easier to cache all of this data and reduce the risk that Phabricator is impaired by heavy traffic to a Phame blog post. We've discussed re-using the old defunct (currently just a redirect) `techblog.wikimedia.org` as the pretty and cacheable entrypoint. There's some configuration work to do on the phame side, as well as DNS and edge cache support. Probably this public-facing URI will not allow authentication at all (readonly), enforced at the cache layer by stripping Authorization/Cookie headers. (This task emerged from a discussion of Phame blogging at the SRE offsite.)

**Steps to Reproduce (tentative)** 1) Create a new blog entry at https://phabricator.wikimedia.org/phame/blog/`{id_number}` 2) Browse to the new blog entry via https://techblog.wikimedia.org/`{id_number}` **Actual Results** Blog page is served directly from Phabricator. Blog entry URLs are ugly. **Requested Results** Page is served from Wikimedia CDN cache if possible. Blog URLs are prettier. Brandon suggested that, with the creation of a specific URL (subdomain?) particular to Phame, it would be much easier to cache all of this data and reduce the risk that Phabricator is impaired by heavy traffic to a Phame blog post. We've discussed re-using the old defunct (currently just a redirect) `techblog.wikimedia.org` as the pretty and cacheable entrypoint. There's some configuration work to do on the phame side, as well as DNS and edge cache support. Probably this public-facing URI will not allow authentication at all (readonly), enforced at the cache layer by stripping Authorization/Cookie headers. (This task emerged from a discussion of Phame blogging at the SRE offsite.)

**Steps to Reproducee (tentative)** 1) Create a new blog entry at https://phabricator.wikimedia.org/phame/blog/`{id_number}` 2) Browse to the new blog entry via https://techblog.wikimedia.org/`{id_number}` **Actual Results** Blog page is served directly from Phabricator. Blog entry URLs are ugly. **Requested Results** Page is served from Wikimedia CDN cache if possible. Blog URLs are prettier. Brandon suggested that, with the creation of a specific URL (subdomain?) particular to Phame, it would be much easier to cache all of this data and reduce the risk that Phabricator is impaired by heavy traffic to a Phame blog post. We've discussed re-using the old defunct (currently just a redirect) `techblog.wikimedia.org` as the pretty and cacheable entrypoint. There's some configuration work to do on the phame side, as well as DNS and edge cache support. Probably this public-facing URI will not allow authentication at all (readonly), enforced at the cache layer by stripping Authorization/Cookie headers. (This task emerged from a discussion of Phame blogging at the SRE offsite.)