Bug #3120
closed
Create a robots.txt file in /opt/rudder/share/load-page to prevent an apache error log flooding
Added by Matthieu CERDA almost 12 years ago.
Updated over 9 years ago.
Description
We should create a robots.txt file in /opt/rudder/share/load-page to prevent the apache error log from beeing cluttered by lots of:
[Mon Dec 31 11:05:04 2012] [error] [client 127.0.0.1] File does not exist: /opt/rudder/share/load-page/robots.txt
They are here because some clients (like wget, curl, ...) by default are trying to access this file to check if there is any explicit access prohibition.
- Status changed from New to 8
- Assignee set to Matthieu CERDA
- Target version changed from 2.3.10 to 2.3.11
- Project changed from Rudder to 34
- Category deleted (
11)
- Target version changed from 2.3.11 to 2.3.12
- Target version changed from 2.3.12 to 2.3.13
- Target version changed from 2.3.13 to 84
- Target version changed from 84 to 2.4.7
- Target version changed from 2.4.7 to 2.4.8
- Target version changed from 2.4.8 to 2.4.9
- Target version changed from 2.4.9 to 2.4.10
- Target version changed from 2.4.10 to 2.4.11
- Target version changed from 2.4.11 to 2.4.12
- Target version changed from 2.4.12 to 2.4.13
- Target version changed from 2.4.13 to 2.6.11
Since Support for 2.4 branch is over, retargeting this issue to 2.6
- Target version changed from 2.6.11 to 2.8.3
Targetting to 2.8 as it is the first version to have a clear segmentation and configuration for the loading page and aliases :)
- Status changed from 8 to Pending technical review
- Assignee changed from Matthieu CERDA to Jonathan CLARKE
- % Done changed from 0 to 100
- Pull Request set to https://github.com/Normation/rudder/pull/434
- Status changed from Pending technical review to Pending release
- Status changed from Pending release to Released
This bug has been fixed in Rudder 2.8.3, which was released today.
Check out:
- Project changed from 34 to Rudder
- Category set to Packaging
Also available in: Atom
PDF