On 3/5/19 12:24 PM, John Hardin wrote:
On Tue, 5 Mar 2019, Bill Cole wrote:
On 5 Mar 2019, at 12:33, John Hardin wrote:
Attempting to grab the latest published rules update (using a utility
script I wrote) I get this:
Latest revision: 1854751
wget https://buildbot.spamassassin.org/updates/1854751.tar.gz ...
That host is not in the mirror list at
http://spamassassin.apache.org/updates/MIRRORED.BY
Or https://svn.apache.org/repos/asf/spamassassin/site/updates/MIRRORED.BY
Agreed it doesn't affect sa-update.
Retrieving from buildbot was working up until recently. Did something on
buildbot change?
Buildbot was never setup a few years ago when the hosting "issue"
happened an I spent months getting the ruleqa/masscheck part working
again so we would give sa-update something to do again.
Basically all of those DNS hostnames were aliases to similar places on
the old server a few years ago from what I was able to piece together.
When I had to switch to a different web server for port 80 web traffic a
few days ago because the redirect to https wasn't working properly with
the , this must have accidentally stopped working.
See the following email thread in the dev and sysadmins list about the
"AllowEncodedSlashes" directive not working in the port 80 virtualhost
redirect to 443:
Re: ruleqa redirection from http to https is mangling the url
Dave
