src/lib/libfetch/common.c, branch release/10.1.0

MFC: r267131, r267132, r267133, r268493, r268671

2014-07-20T00:29:41Z

Use NULL instead of 0 (Patch by Sascha Wildner for Dragonfly) Remove unnecessary semicolons (Patch by Sascha Wildner for Dragonfly) Add support for arbitrary http requests [1] Support EAGAIN in fetch_writev Submitted by: Alex Hornung [1] Reviewed by: des

MFH (r266291): look for root certs in /usr/local first

2014-05-24T22:50:58Z

MFH (r260904): fix format string

2014-02-27T13:27:04Z

MFH (r261230, r261263): fix buffering issues MFH (r261284): bump copyright

MFC r258347,r258349:

2013-11-29T21:13:30Z

Support SNI in libfetch SNI is Server Name Indentification which is a protocol for TLS that indicates the host that is being connected to at the start of the handshake. It allows to use Virtual Hosts on HTTPS. PR: kern/183583 Approved by: bapt (implicit) Approved by: re (gjb)

Implement certificate verification, and many other SSL-related

2013-07-26T15:53:43Z

imrovements; complete details in the PR. PR: kern/175514 Submitted by: Michael Gmelin MFC after: 1 week

libfetch: Avoid SIGPIPE on network connections.

2012-05-28T19:22:23Z

To avoid unexpected process termination from SIGPIPE when writing to a closed network connection, enable SO_NOSIGPIPE on all network connections. The POSIX standard MSG_NOSIGNAL is not used since it requires modifying all send calls to add this flag. This is particularly nasty for SSL connections. Reviewed by: des Tested by: bapt MFC after: 5 days

Since the socket is non-blocking, it is necessary to use select(2) even

2012-04-30T12:11:45Z

when there is no timeout, because read(2) will return immediately if there is no data waiting in the TCP buffer, causing fetch_read() to busy-loop on slow connections. MFC after: 3 weeks Noticed by: Yanhui Shen

Fix two nits in previous commit pointed out by pjd@.

2012-01-23T09:23:07Z

MFC after: 3 weeks

Fix two issues related to the use of SIGINFO in fetch(1) to display

2012-01-18T15:13:21Z

progress information. The first is that fetch_read() (used in the HTTP code but not the FTP code) can enter an infinite loop if it has previously been interrupted by a signal. The second is that when it is interrupted, fetch_read() will discard any data it may have read up to that point. Luckily, both bugs are extremely timing-sensitive and therefore difficult to trigger. PR: bin/153240 Submitted by: Mark MFC after: 3 weeks

latin1 -> utf8

2011-10-19T11:43:51Z