AnqiCMS (AnqiCMS) Template Tag Manual
After replacing the certificate, the style is missing half, usually due to the residual http resources in the https page being blocked by the browser. The cleaning order is to first locate the residual references, then batch replace them with internal relative addresses or encrypted addresses according to the main text data, template, and configuration, and finally close the jump rules together.
Changing from HTTP to HTTPS is not just about installing certificates. It also involves: the 301 redirect rules for old addresses, hardcoded absolute addresses within the site, the protocol in the sitemap and robots, pseudo-static and standard address configuration, as well as hard-coded links in navigation and single-page applications. The recommended sequence is to first handle certificates and redirects, then perform bulk replacements, and finally update the checklist files and review mixed content.
The default validity period of the HTTPS certificate is ninety days, and renewal should not wait until the browser alarms. Automatic renewal should be as a fixed scheduled task in the deployment process, after the certificate is issued and before the service is reloaded, and it is recommended to trigger once every sixty days. To confirm that it has been renewed, you need to check the actual expiration date of the online certificate, and also check the old address redirection and mixed content, and keep a backup before changing the certificate.
Dynamic compression consumes CPU each time a request is made and is limited by minimum length and type list; pre-compression shifts the cost to the publishing stage, sending the existing .gz file directly, but ensuring that the modification time of the original file matches that of the compressed file. The two layers are not substitutes: the content management program is responsible for generation, and the web server is responsible for choosing the sending method based on the client and type, with the help of caching and reverse proxy layers to achieve stable loading speed benefits.
Adding version number still hits old files, usually because the response header and filename strategy are not matched: max-age is calculated from the moment the response is generated on the source site instead of the moment it is received, without must-revalidate after expiration, it may continue to reuse outdated copies; s-maxage only manages shared caching and overrides max-age; immutable should be used with version numbers to avoid unnecessary conditional requests. The cache duration for page content and static resources should be configured separately.
A backup of only the database will leave a very specific gap: after the restore, the article list is still there, but the images, attachments, and static resources in the main text all point to invalid addresses. The scope of a complete backup should cover both data and static files, and regular recovery drills should be conducted. The trash can only cover deleted documents and cannot replace backups; the location relationship of the backup files themselves should also be recorded with the site deployment directory and upload directory.
When automatic updates are enabled, there is a big difference in the default orientation between major and minor versions: An official operation manual of a mainstream program states that most sites default to enabling automatic updates, covering four categories: core, plugins, themes, and translation files. Since version 5.6, new installations have default automatic updates for both minor and major versions. For enterprise sites, a more stable compromise is to automatically update minor versions, manually evaluate major versions, and confirm the backup range before the upgrade to include both data and static files.
How to handle the filing number when changing the server of the website, the judgment standard is whether the access provider has changed: When changing the access provider, the access filing should be handled at the new access provider, and the change of materials for the same subject should go through the change filing and require bureau review. This article clarifies two actions, the impact on access during the review period, and the most easily overlooked one when multiple sites share a domain name.
Use the same program to deploy with one click on the panel or configure layer by layer with the command line, only once during the installation stage, the difference lies in the four daily actions of adding new sites, certificate renewal, log rotation and backup recovery. This article compares the workload of two paths for each action and explains why it is necessary to compare the environment first before comparing the data when migrating.
After reverse proxy, the source address becomes the address of the proxy server, because the proxy defaults to not transmitting the original Host and Connection headers. The required request headers are Host and X-Forwarded-For: the former passes the original domain name through a variable, and the latter appends the client address. When multiple sites share a single entry point, a missing Host can cause a site error, and the port mapping relationships should also be recorded in the deployment document.
