Skip to content
Snippets Groups Projects
Select Git revision
  • master-tlmsp default
  • master-tlmsp-latest-curl
  • bagder/runtests-duration
  • bagder/disable-progress-meter
  • master protected
  • bagder/parallel-transfers
  • bagder/hsts-rebased
  • QUIC
  • bagder/FOLLOW_IGNORE_CUSTOM
  • bagder/test-when-disabled
  • jay/test
  • bagder/curl-better-disabled-options
  • bagder/wolfssh
  • dfandrich/ci
  • TFO-windows
  • bagder/schannel-verifyhost
  • bagder/mbedtls-ssl_read-zero
  • bagder/wolfssl-crl
  • curl-7_65_1
  • curl-7_65_0
  • curl-7_64_1
  • curl-7_64_0
  • curl-7_63_0
  • curl-7_62_0
  • curl-7_61_1
  • curl-7_61_0
  • curl-7_60_0
  • curl-7_59_0
  • curl-7_58_0
  • curl-7_57_0
  • curl-7_56_1
  • curl-7_56_0
  • curl-7_55_1
  • curl-7_55_0
  • curl-7_54_1
  • curl-7_54_0
  • curl-7_53_1
  • curl-7_53_0
38 results
Compare
user avatar
connect: use UDP correctly
Daniel Stenberg authored 
The idea that the protocol and socktype is part of name resolving in the
libc functions is nuts. We keep the name resolver functions assume
TCP/STREAM and we make sure that when we want to connect to a UDP
service we use the correct UDP/DGRAM set instead. This bug was because
the ->protocol field was not always set correctly.

This bug was only affecting ipv6-disabled non-cares non-threaded builds.

Bug: http://curl.haxx.se/bug/view.cgi?id=3154436
Reported by: "dperham"
08a65b10
History
user avatar 08a65b10
History
Name Last commit Last update
..