[MacPorts] #28499: libiconv: checksum failure because of local proxy blocking facebook (was: Checksum mismatch for libiconv-1.13.1.tar.gz)

[MacPorts]

#28499: libiconv: checksum failure because of local proxy blocking facebook
--------------------------------------+-------------------------------------
 Reporter:  artem.zavyalov@…          |       Owner:  ryandesign@…           
     Type:  defect                    |      Status:  new                    
 Priority:  Normal                    |   Milestone:                         
Component:  ports                     |     Version:  1.9.2                  
 Keywords:                            |        Port:  libiconv               
--------------------------------------+-------------------------------------

Comment(by ryandesign@…):

 You cannot pick the distfiles mirror used; MacPorts picks it for you based
 on lowest ping time. If your company's DNS server has remapped all
 Facebook hostnames to its own proxy server, that would explain why that
 server has the lowest ping time for you.

 You can [wiki:ProblemHotlist#fetch-failures manually download distfiles
 and place them in the right place].

 [changeset:71463 I added the Facebook mirrors to MacPorts last September]
 because they have mirrors for many projects and I assumed they would be
 fast, but I did not consider that many businesses would block Facebook,
 and might not be so discriminating about how they do this. Still, this is
 the first report I've seen about it. Could you ask your proxy
 administrators to relax their block slightly? I understand the need to
 block users from accessing www.facebook.com, maybe even *.facebook.com,
 but there's no need to block users from accessing their mirrors of open-
 source software at mirror.facebook.net.

 In addition, your proxy's administrator should reconfigure the web server
 that produces their "This URLs or Page has been blocked" message. They are
 currently returning an HTTP status code (probably "200 OK") which means
 everything is ok, the request was successfully processed. This is clearly
 not the case. They should pick another HTTP status code which indicates
 that some error has occurred; MacPorts would have seen that error code and
 tried a different mirror. "404 Not Found" or "403 Forbidden" aren't
 exactly right, but would be better than "200 OK".

-- 
Ticket URL: <https://trac.macports.org/ticket/28499#comment:5>
MacPorts <http://www.macports.org/>
Ports system for Mac OS