Closed renoirb closed 9 years ago
After some tests I realized that the site is slower than old production. There might be server details that didn’t follow up.
From every app VM, check if:
HTTP PURGE
Was
2015-03-20 22:05:22 app1 wpwiki: SquidPurgeClient (docs.webplatform.org): unexpected status code: 301 Moved Permanently
And there should not be.
Moved notes to wiki https://docs.webplatform.org/wiki/WPD:Infrastructure/architecture/Things_to_consider_when_we_expose_service_via_Fastly_and_Varnish
Feature works. More improvements to come later once documentation and notes are gathered.
After some tests I realized that the site is slower than old production. There might be server details that didn’t follow up.
Tasks
From every app VM, check if:
HTTP PURGE
to Fastly on save, and that it worksLog says
SquidPurgeClient Unexpected status code: 301
Was
And there should not be.
Reference