Robots.txt file is cached by Full Page Cache of Magento

[dandrikop]

Preconditions and environment

When you change the contents of the robots.txt file via Content > Design > Configuration > Search Engine Robots, the changes do not become immediately available on the front-end of the Magento website even if you refresh the Configuration cache via System > Cache Management. It seems that the page https://www.example.com/robots.txt is cached by the Full Page Cache of Magento. I tested that on Magemto 2.4.6-p7 by using REDIS as the Full Page Cache of Magento.

Steps to reproduce

1. Visit the robots.txt file via the link: https://www.example.com/robots.txt
2. Change the content of the robots.txt file via Content > Design > Configuration > Search Engine Robots
3. Refresh the Configuration cache via System > Cache Management
4. Visit again the robots.txt file via the link: https://www.example.com/robots.txt

Expected result

The new content of the robots.txt file should be viewed at https://www.example.com/robots.txt

Actual result

The old content of the robots.txt file is viewed at "https://www.example.com/robots.txt".

Additional information

The only way to make the changes of the robots.txt available at the front-end of the Magento website is by flushing the Full Page Cache. However, this work-around is not appropriate for the following reasons:

1. Robots.txt is considered configuration, and so any configuration change should become available immediately.
2. The Full Page Cache significantly improves the performance of the Magento front-end.
3. The Full Page Cache may need several days to be filled again even by using intensive Cache warmers.

So, it's worth flushing the Full Page Cache only when there are applied changes affecting a large number of pages, such as the installation of a new module, or the update of existing module.

Release note

No response

Triage and priority

• [ ] Severity: S0 - Affects critical data or functionality and leaves users without workaround.
• [ ] Severity: S1 - Affects critical data or functionality and forces users to employ a workaround.
• [X] Severity: S2 - Affects non-critical data or functionality and forces users to employ a workaround.
• [ ] Severity: S3 - Affects non-critical data or functionality and does not force users to employ a workaround.
• [ ] Severity: S4 - Affects aesthetics, professional look and feel, “quality” or “usability”.

[m2-assistant[bot]]

Hi @dandrikop. Thank you for your report. To speed up processing of this issue, make sure that the issue is reproducible on the vanilla Magento instance following Steps to reproduce.

• For more details, review the Magento Contributor Assistant documentation.
• Add a comment to assign the issue: @magento I am working on this

• To learn more about issue processing workflow, refer to the Code Contributions.

  Join Magento Community Engineering Slack and ask your questions in #github channel. :warning: According to the Magento Contribution requirements, all issues must go through the Community Contributions Triage process. Community Contributions Triage is a public meeting. :clock10: You can find the schedule on the Magento Community Calendar page. :telephone_receiver: The triage of issues happens in the queue order. If you want to speed up the delivery of your contribution, join the Community Contributions Triage session to discuss the appropriate ticket.

[m2-assistant[bot]]

Hi @engcom-Bravo. Thank you for working on this issue. In order to make sure that issue has enough information and ready for development, please read and check the following instruction: :point_down:

• [ ] 1. Verify that issue has all the required information. (Preconditions, Steps to reproduce, Expected result, Actual result).
• [ ] 2. Verify that issue has a meaningful description and provides enough information to reproduce the issue.
• [ ] 3. Add Area: XXXXX label to the ticket, indicating the functional areas it may be related to.
• [ ] 4. Verify that the issue is reproducible on 2.4-develop branch
  Details

  - If the issue is reproducible on 2.4-develop branch, please, add the label Reproduced on 2.4.x.
  - If the issue is not reproducible, add your comment that issue is not reproducible and close the issue and stop verification process here!
• [ ] 5. Add label Issue: Confirmed once verification is complete.
• [ ] 6. Make sure that automatic system confirms that report has been added to the backlog.

[engcom-Bravo]

Hi @dandrikop,

Thanks for your reporting and collaboration.

We have verified the issue in Latest 2.4-develop instance and the issue is not reproducible.Kindly refer the screenshots.

The new content of the robots.txt file viewed at https://www.example.com/robots.txt

Kindly recheck the issue in Latest 2.4-develop instance and elaborate the steps to reproduce and please let us know if we are missing anything.

Thanks.