Page MenuHomePhabricator

Fix `cancdn` vs `canCDN` flag
ClosedPublic

Authored by epriestley on Aug 14 2014, 3:35 PM.
Tags
None
Referenced Files
F13360893: D10264.diff
Tue, Jun 25, 12:23 PM
F13345771: D10264.diff
Fri, Jun 21, 11:30 AM
F13329029: D10264.id.diff
Sun, Jun 16, 7:56 PM
F13263764: D10264.id24713.diff
May 27 2024, 12:11 PM
F13263763: D10264.id24718.diff
May 27 2024, 12:10 PM
F13215992: D10264.id24713.diff
May 17 2024, 9:39 PM
F13209036: D10264.id.diff
May 16 2024, 9:19 PM
F13202713: D10264.diff
May 14 2024, 11:02 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).