Why Does the Page Fail to Be Refreshed After WTP Is Enabled?
Web Tamper Protection (WTP) supports only caching of static web pages. Perform the following steps to fix this issue:
- Log in to the management console.
- Click in the upper left corner of the management console and select a region or project.
- Click in the upper left corner and choose Web Application Firewall under Security & Compliance.
- In the navigation pane on the left, choose Policies.
- Click the name of the target policy to go to the protection configuration page.
- Click the Web Tamper Protection configuration area and check whether this function is enabled.
- If this function is enabled (), go to Step 7.
- If this function is disabled (), click to enable the function. Refresh the page several minutes later.
- On the displayed page, check whether the domain name and path are correct.
- If they are correct, go to Step 8.
- If they are incorrect, click Delete in the Operation column to delete the rule. Then, click Add Rule above the rule list and configure another rule. For details, see Configuring a Web Tamper Protection Rule.
After the rule is added successfully, refresh the page several minutes later. Then, access the page again.
- In the row containing the web tamper protection rule, click Update Cache in the Operation column.
If the content of a protected page is modified, you must update the cache. Otherwise, WAF always returns the most recently cached content.
After updating the cache, refresh the page and access the page again. If the page is still not updated, contact technical support.
Protection Rules FAQs
- How Do I Switch the Mode of Basic Web Protection from Log Only to Block?
- Which Protection Levels Can Be Set for Basic Web Protection?
- What Is the Peak Rate of CC Attack Protection?
- When Is Cookie Used to Identify Users?
- What Are the Differences Between Rate Limit and Allowable Frequency in a CC Rule?
- Why Cannot the Verification Code Be Refreshed When Verification Code Is Configured in a CC Attack Protection Rule?
- Can a Precise Protection Rule Take Effect in a Specified Period?
- Can a Path Containing # Be Matched in a Precise Protection Rule?
- How Can I Allow Access from .js Files?
- Can I Batch Add IP Addresses to a Blacklist or Whitelist Rule?
- Can I Import or Export a Blacklist or Whitelist into or from WAF?
- How Do I Block Abnormal IP Addresses?
- Why Does a Requested Page Fail to Respond to the Client After the JavaScript-based Anti-Crawler Is Enabled?
- Is There Any Impact on Website Loading Speed If Other Crawler Check in Anti-Crawler Is Enabled?
- How Does JavaScript Anti-Crawler Detection Work?
- In Which Situations Will the WAF Policies Fail?
- How Do I Allow Requests from Only IP Addresses in a Specified Geographical Region?
- Which of the WAF Protection Rules Support the Log-Only Protective Action?
- How Do I Allow Only Specified IP Addresses to Access Protected Websites?
- Which Protection Rules Are Included in the System-Generated Policy?
- Why Does the Page Fail to Be Refreshed After WTP Is Enabled?
- What Are the Differences Between Blacklist/Whitelist Rules and Precise Protection Rules on Blocking Access Requests from Specified IP Addresses?
- What Do I Do If a Scanner, such as AppScan, Detects that the Cookie Is Missing Secure or HttpOnly?
Feedback
Was this page helpful?
Provide feedbackThank you very much for your feedback. We will continue working to improve the documentation.See the reply and handling status in My Cloud VOC.
For any further questions, feel free to contact us through the chatbot.
Chatbotmore