[Gluster-infra] [Bug 1490993] Redirect fun with lists

https://bugzilla.redhat.com/show_bug.cgi?id=1490993 Amye Scavarda changed: What|Removed |Added Status|ASSIGNED|CLOSED

[Gluster-infra] [Bug 1490993] Redirect fun with lists

https://bugzilla.redhat.com/show_bug.cgi?id=1490993 --- Comment #15 from Amye Scavarda --- Here's what I'll do: It seems to be working at the moment, so let me see if it continues to work, and what it does to our traffic to have the redirect through the direct WordPress

[Gluster-infra] [Bug 1490993] Redirect fun with lists

https://bugzilla.redhat.com/show_bug.cgi?id=1490993 --- Comment #14 from Amye Scavarda --- Here's what I'll do: It seems to be working at the moment, so let me see if it continues to work, and what it does to our traffic to have the redirect through the direct WordPress

[Gluster-infra] [Bug 1490993] Redirect fun with lists

https://bugzilla.redhat.com/show_bug.cgi?id=1490993 Karsten Wade changed: What|Removed |Added Flags|

[Gluster-infra] [Bug 1490993] Redirect fun with lists

https://bugzilla.redhat.com/show_bug.cgi?id=1490993 --- Comment #11 from Karsten Wade --- OK, that helped a lot -- I didn't prepend the rule with ^ and that fixed this case so the rewrite/redirect is now working for hardlinked mailing list links. -- You are receiving this

[Gluster-infra] [Bug 1490993] Redirect fun with lists

https://bugzilla.redhat.com/show_bug.cgi?id=1490993 M. Scherer changed: What|Removed |Added Assignee|b...@gluster.org|a...@redhat.com

[Gluster-infra] [Bug 1490993] Redirect fun with lists

https://bugzilla.redhat.com/show_bug.cgi?id=1490993 --- Comment #9 from Karsten Wade --- One more point -- we should also make sure that www/mailman(.*) also redirects to lists.gluster.org/mailman$1. -- You are receiving this mail because: You are on the CC list for the

[Gluster-infra] [Bug 1490993] Redirect fun with lists

https://bugzilla.redhat.com/show_bug.cgi?id=1490993 --- Comment #8 from Karsten Wade --- I'll bring the discussion back to Michael, we'll figure out a plan & timeline, and return with those to this ticket. Once we have a plan in place here, we'll reassign to you for ACK on

[Gluster-infra] [Bug 1490993] Redirect fun with lists

https://bugzilla.redhat.com/show_bug.cgi?id=1490993 Amye Scavarda changed: What|Removed |Added Status|NEW |ASSIGNED

[Gluster-infra] [Bug 1490993] Redirect fun with lists

https://bugzilla.redhat.com/show_bug.cgi?id=1490993 --- Comment #6 from Karsten Wade --- New ideas since #c4 didn't work: Source URL: .*gluster.org/pipermail/(.+) Target URL: lists.gluster.org/pipermail/$1 ... or ... Source URL: .*gluster.org/pipermail/(.*) Target

[Gluster-infra] [Bug 1490993] Redirect fun with lists

https://bugzilla.redhat.com/show_bug.cgi?id=1490993 --- Comment #5 from Amye Scavarda --- This doesn't pick up any hits, not sure why. I'm using "https://www.gluster.org/pipermail/gluster-devel/2017-August/thread.html; as a test URL, so let's keep poking at it. -- You are

[Gluster-infra] [Bug 1490993] Redirect fun with lists

https://bugzilla.redhat.com/show_bug.cgi?id=1490993 --- Comment #4 from Karsten Wade --- The WPEngine how to recommends this pattern: Name: Redirect catch all Domain: www.domain.com Source: ^/thisiswhere/myfileswere/(.+) Destination: /thisiswhere/myfilesmovedto/$1 Redirect

[Gluster-infra] [Bug 1490993] Redirect fun with lists

https://bugzilla.redhat.com/show_bug.cgi?id=1490993 --- Comment #3 from Karsten Wade --- Created attachment 1324980 --> https://bugzilla.redhat.com/attachment.cgi?id=1324980=edit WPEngine UI screenshot -- You are receiving this mail because: You are on the CC list for the

[Gluster-infra] [Bug 1490993] Redirect fun with lists

https://bugzilla.redhat.com/show_bug.cgi?id=1490993 --- Comment #2 from Karsten Wade --- One fix for the source URL: .*gluster.org/pipermail.* (Reading through https://wpengine.com/support/regex/ ) -- You are receiving this mail because: You are on the CC list for the

[Gluster-infra] [Bug 1490993] Redirect fun with lists

https://bugzilla.redhat.com/show_bug.cgi?id=1490993 --- Comment #1 from Karsten Wade --- Looking at the WP UI for this, the source URL supports regexp but I'm not sure how the target URL gets the matching string fed in. So the source regexp could be (at least to try):