Hmm, well honestly in this day and age, with everything moving to https I considered just disabling port 80 access altogether. But I'll look into what I need to do to get your request working.

-Erinn


On 02/23/2018 09:47 AM, Adrian Reber wrote:
On Fri, Feb 23, 2018 at 04:19:54PM +0000, Erinn D Looney-Triggs wrote:
Yeah, seems to be because everyone's Cron jobs fire at the top of the hour and the site gets overwhelmed. You run the same thing now, it'll work. We'll be adjusting resources to get things working.
Sounds good. Our crawler still cannot reach your mirror:

send: u'HEAD /fedora/epel/ HTTP/1.1\r\nHost: mirror.colorado.edu\r\nAccept-Encoding: identity\r\nConnection: Keep-Alive\r\nPragma: no-cache\r\nUser-Agent: mirrormanager-crawler/0.1 (+https://github.com/fedora-infra/mirrormanager2/)\r\n\r\n'
reply: 'HTTP/1.1 404 Not Found\r\n'
header: Date: Fri, 23 Feb 2018 16:33:38 GMT
header: Server: Apache/2.4.6 (Red Hat Enterprise Linux) OpenSSL/1.0.2k-fips
header: Strict-Transport-Security: max-age=15768000
header: Keep-Alive: timeout=5, max=100
header: Connection: Keep-Alive
header: Content-Type: text/html; charset=iso-8859-1

Our crawler still tries to access your mirror via http with a HEAD
request, to see if a basic connectivity is there. You have redirect
to https, but that does only work for GET requests.

To test: curl http://mirror.colorado.edu/fedora/epel/ -vI

Gives me a 404

		Adrian


_______________________________________________
Mirror-admin mailing list -- mirror-admin@lists.fedoraproject.org
To unsubscribe send an email to mirror-admin-leave@lists.fedoraproject.org