I would employ curl to check headers on a request, though any tool of choice should work: curl -I URL
For the superb-dca2 mirror, I see it’s running nginx/0.8.55. Is that what you see? $ curl -I http://superb-dca2.dl.sourceforge.net/project/expat/expat/2.1.0/expat-2.1.0.tar.gz HTTP/1.1 200 OK Server: nginx/0.8.55 Date: Mon, 28 Jul 2014 19:24:23 GMT Content-Type: application/x-gzip Content-Length: 562616 Last-Modified: Sat, 24 Mar 2012 19:19:12 GMT Connection: close Accept-Ranges: bytes Similarly, the macports mirror is lighttpd: $ curl -I http://cjj.kr.distfiles.macports.org/expat/expat-2.1.0.tar.gz HTTP/1.1 200 OK Content-Type: application/x-gzip Accept-Ranges: bytes ETag: "683330017" Last-Modified: Tue, 04 Sep 2012 23:59:26 GMT Content-Length: 562616 Date: Mon, 28 Jul 2014 19:25:24 GMT Server: lighttpd/1.4.28 If those are different, and the “replacement” server signature doesn’t appear reasonable, we might start looking into DNS records to see if they’re being hijacked. On Jul 28, 2014, at 15:22, Sam Finn <lsf...@gmail.com> wrote: > Doesn’t a 403 indicate that the server received and understood the request, > but refused to act on it? In any event, there is no proxy and I’ve checked > that my firewalls (the mac os firewall and intego net barrier) are down. Am I > missing something? > > Other information that may (or may not) be helpful: > * I’m reaching the network through an apple AirPort Extreme, which is > providing both NAT and DHCP services > * The computer I’m working on right now is set-up as the default host (i.e., > it has a DHCP reservation, whose IP is the default host). > > Thanks very much for any and all help! _______________________________________________ macports-users mailing list macports-users@lists.macosforge.org https://lists.macosforge.org/mailman/listinfo/macports-users
