Page MenuHomePhabricator

Fix `cancdn` vs `canCDN` flag
ClosedPublic

Authored by epriestley on Aug 14 2014, 3:35 PM.
Tags
None
Referenced Files
F15461688: D10264.id24718.diff
Tue, Apr 1, 10:20 AM
F15444499: D10264.id.diff
Thu, Mar 27, 9:49 AM
F15443847: D10264.id24718.diff
Thu, Mar 27, 6:29 AM
F15443666: D10264.id24713.diff
Thu, Mar 27, 5:34 AM
F15440814: D10264.id24713.diff
Wed, Mar 26, 2:45 PM
F15440708: D10264.diff
Wed, Mar 26, 2:14 PM
F15421016: D10264.id24713.diff
Fri, Mar 21, 8:16 PM
F15413866: D10264.diff
Wed, Mar 19, 9:47 PM
Subscribers

Details

Reviewers
btrahan
Maniphest Tasks
T5884: Existing files not set to CDNable
Commits
Restricted Diffusion Commit
rPae1a821b658a: Fix `cancdn` vs `canCDN` flag
Summary

Ref T5884. We migrated to add a canCDN flag, but the code looks for a cancdn flag.

If this fixes the issue, I'll migrate cancdn to canCDN in the next diff.

Test Plan

Viewed some files, including old files, and saw the cacheability I expected.

Diff Detail

Repository
rP Phabricator
Lint
Lint Skipped
Unit
Tests Skipped

Event Timeline

epriestley retitled this revision from to Fix `cancdn` vs `canCDN` flag.
epriestley updated this object.
epriestley edited the test plan for this revision. (Show Details)
epriestley added a reviewer: btrahan.
btrahan edited edge metadata.
This revision is now accepted and ready to land.Aug 14 2014, 6:49 PM
epriestley updated this revision to Diff 24718.

Closed by commit rPae1a821b658a (authored by @epriestley).