[MacPorts] #64729: aom - port fails to download

[MacPorts]

#64729: aom - port fails to download
-------------------------+--------------------
  Reporter:  mouse07410  |      Owner:  (none)
      Type:  defect      |     Status:  new
  Priority:  Normal      |  Milestone:
 Component:  ports       |    Version:
Resolution:              |   Keywords:
      Port:  aom         |
-------------------------+--------------------

Comment (by ryandesign):

 Replying to [comment:5 mouse07410]:
 > {{{
 > :debug:fetch Backtrace: error:1400410B:SSL
 routines:CONNECT_CR_SRVR_HELLO:wrong version number
 > }}}

 Googling this error, it seems to say that it occurs when you try to send
 https traffic to a server that does not support https (such as an http
 server). All of our servers are surely not misconfigured in the same way
 at the same time, therefore I suggest there is a problem with your
 computer (like an antivirus program that is monitoring and interfering
 with your network traffic) or with a proxy server that you have configured
 your computer to use.


 Replying to [comment:6 mouse07410]:
 > Further digging by my colleague brought up this:
 https://apple.stackexchange.com/questions/432353/updated-macports-curl-
 implementation-behaves-differently-from-previous-version-a

 That page appears to discuss this error:
 {{{
 curl: (35) error:0A000152:SSL routines::unsafe legacy renegotiation
 disabled
 }}}
 which is different from the error you reported so I don't see the
 relevance.

 > The short answer is - {{{curl}}} port default variant should something
 different from {{{+ssl}}}. {{{+darwinssl}}} (using system TLS) or
 {{{+gnutls}}} (using Gnu TLS that {{{wget}}} default uses).
 >
 > I'd appreciate if the {{{curl}}} port default variant was changed.

 I have considered changing the curl port's default variant, however I
 don't see that it has anything to do with the problem you're experiencing.
 MacPorts does not use MacPorts curl to download anything, unless you have
 built MacPorts from source and told it to do so. If you have, then you
 could reinstall curl with a different variant, if that helps you. But I
 don't see how it could help solve the problem that https servers are
 apparently sending non-https responses only to your computer.

-- 
Ticket URL: <https://trac.macports.org/ticket/64729#comment:9>
MacPorts <https://www.macports.org/>
Ports system for macOS