Remove old bbPress1 Search blocking

Currently requests to /support/search.php and /plugins/search.php are blocked for GoogleBot at the LB
Since neither of these URLs are in use today, can we remove these blocks?

Low-priority ref #4765-meta

#prio3

#4765-meta

Update some 302 redirects to 301s

Hi, as per #4630-meta can we update the following 302 redirects to 301’s?

  • chat.wordpress.org
  • phpdoc.wordpress.org
  • wordpress.org/extend/

Additional ones via #4075-meta

  • wordpress.org/forums/
  • wordpress.org/tags/*

Here’s a diff that should apply to the web role:

Index: wporg-redirects.conf
===================================================================
--- wporg-redirects.conf	(revision 9066)
+++ wporg-redirects.conf	(working copy)
@@ -112 +112 @@
-	return 302 https://make.wordpress.org/chat/;
+	return 301 https://make.wordpress.org/chat/;
@@ -134 +134 @@
-	return 302 https://developer.wordpress.org/reference/;
+	return 301 https://developer.wordpress.org/reference/;
Index: wporg-wordpress.org
===================================================================
--- wporg-wordpress.org	(revision 9066)
+++ wporg-wordpress.org	(working copy)
@@ -36 +36 @@
-	rewrite ^/extend/?$ https://wordpress.org/ redirect;
+	rewrite ^/extend/?$ https://wordpress.org/ permanent;
@@ -88 +88 @@
-		rewrite ^ /support/ redirect;
+		rewrite ^ /support/ permanent;
@@ -91 +91 @@
-		rewrite ^ /support/ redirect;
+		rewrite ^ /support/ permanent;
@@ -99 +99 @@
-		rewrite ^/tags/(.*) /support/topic-tag/$1 redirect;
+		rewrite ^/tags/(.*) /support/topic-tag/$1/ permanent;

#prio3

#4075-meta, #4630-meta

Redirect downloads.wordpress.org/?$ to wordpress.org/download/ Currently…

Redirect downloads.wordpress.org/?$ to wordpress.org/download/

Currently if a user visits https://downloads.wordpress.org/ url into a browser, they hit a nginx 404, The nginx configuration isn’t setup to allow an index.php file to be served for that domain, so could we either have it redirect the root to wordpress.org/download/ or haveindex.php support enabled?

Ref: https://meta.trac.wordpress.org/ticket/4654

Thanks!
#prio3

Blackberry Mobile App Trac being targeted for hacks

We’ve noticed an influx of new entries in the BlackBerry Trac that are hacky/spammy. Example:

https://blackberry.trac.wordpress.org/#no1
https://blackberry.trac.wordpress.org/ticket/263

Can we block this from happening for the existing bad accounts posting and also prevent it from happening further? The BlackBerry app is also dead (for several years now) so we can freeze the entire site or get rid of it entirely.

#mobile #prio3

Make GSOC trac read-only

It’s getting pentested: https://gsoc.trac.wordpress.org/ticket/386

Can we make it read-only, and if not, then maybe back it up and shut it down, or put it behind proxy auth or something? It’d be nice to preserve the content for history, but it’s probably not worth maintaining anymore, and definitely not worth cleaning up after pentesters.

#prio3

Add SSL redirect to pingomatic.com

As per https://meta.trac.wordpress.org/ticket/4245 can we please enable a HTTP -> HTTPS redirect for pingomattic.com that keeps the REQUEST_URI intact?

#prio3

Can bbPress.trac please get Core’s…

Can bbPress.trac please get Core’s Ticket Workflow enabled for it? Same as Meta/BuddyPress already have.

ref: https://meta.trac.wordpress.org/ticket/2508

#prio3 #trac

As per https://meta.trac.wordpress.org/ticket/1639 can we…

As per https://meta.trac.wordpress.org/ticket/1639 can we update all of the Trac instances to have default_charset = utf-8?

A number of Trac instances are set to default_charset = iso-8859-15.

#prio3 #trac

As per https://meta.trac.wordpress.org/ticket/3985 can we…

As per https://meta.trac.wordpress.org/ticket/3985 can we change the behaviour of the out-of-bounds pagination requests from return 404; to instead load /404.php?

It seems most of the 404 handlers in the web role already do this, and it’s only the out-of-bounds pagination rules on the load balancer which have that behaviour.

#prio3

Can I get a deploy…

Can I get a deploy of the codex files?

I made a change to the DotorgRedirect plugin for the codex, to whitelist “wordpress.org” as a valid place for it to redirect to, per request of the docs team: https://wordpress.slack.com/archives/C02RP4WU5/p1543972984189700

So, just need to get that one line change onto the codex.

cc @drewapicture

#prio3