public inbox for gcc-cvs-wwwdocs@sourceware.org help / color / mirror / Atom feed
From: Mark Wielaard <mark@sourceware.org> To: gcc-cvs-wwwdocs@gcc.gnu.org Subject: gcc-wwwdocs branch master updated. 0d8105fd15b33980886283869e980f60f2ca9f04 Date: Fri, 22 Dec 2023 20:51:36 +0000 (GMT) [thread overview] Message-ID: <20231222205136.E130F3858D28@sourceware.org> (raw) This is an automated email from the git hooks/post-receive script. It was generated because a ref change was pushed to the repository containing the project "gcc-wwwdocs". The branch, master has been updated via 0d8105fd15b33980886283869e980f60f2ca9f04 (commit) from 062897ff96bb9651f7a1e152bc2327cbda4ad89e (commit) Those revisions listed above that are new to this repository have not appeared on any other notification email; so we list those revisions in full, below. - Log ----------------------------------------------------------------- commit 0d8105fd15b33980886283869e980f60f2ca9f04 Author: Mark Wielaard <mark@klomp.org> Date: Fri Dec 22 21:46:32 2023 +0100 robots.txt: Disallow a few more bugzilla queries Some spiders are hitting bugzilla hard generating dependency trees or graphs, downloading large attachements or requesting all bugs in xml format. Disallow all that. diff --git a/htdocs/robots.txt b/htdocs/robots.txt index b9fc830d..057c5899 100644 --- a/htdocs/robots.txt +++ b/htdocs/robots.txt @@ -10,4 +10,8 @@ Disallow: /cgit/ Disallow: /svn Disallow: /cgi-bin/ Disallow: /bugzilla/buglist.cgi +Disallow: /bugzilla/show_bug.cgi*ctype=xml* +Disallow: /bugzilla/attachment.cgi +Disallow: /bugzilla/showdependencygraph.cgi +Disallow: /bugzilla/showdependencytree.cgi Crawl-Delay: 60 ----------------------------------------------------------------------- Summary of changes: htdocs/robots.txt | 4 ++++ 1 file changed, 4 insertions(+) hooks/post-receive -- gcc-wwwdocs
reply other threads:[~2023-12-22 20:51 UTC|newest] Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
Reply instructions: You may reply publicly to this message via plain-text email using any one of the following methods: * Save the following mbox file, import it into your mail client, and reply-to-all from there: mbox Avoid top-posting and favor interleaved quoting: https://en.wikipedia.org/wiki/Posting_style#Interleaved_style * Reply using the --to, --cc, and --in-reply-to switches of git-send-email(1): git send-email \ --in-reply-to=20231222205136.E130F3858D28@sourceware.org \ --to=mark@sourceware.org \ --cc=gcc-cvs-wwwdocs@gcc.gnu.org \ /path/to/YOUR_REPLY https://kernel.org/pub/software/scm/git/docs/git-send-email.html * If your mail client supports setting the In-Reply-To header via mailto: links, try the mailto: linkBe sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions for how to clone and mirror all data and code used for this inbox; as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).