On 11/11/2012 01:35 PM, Kristian Fiskerstrand wrote: > On 11/11/2012 11:01 AM, Oscar Koeroo wrote: >> On 10-11-12 20:45, Kristian Fiskerstrand wrote: >>> My crawler use curl as the basis for the requests, and as I connect >>> using the hostname found in server-discovery, whereby I need it to be >>> valid for the purpose of a DNS Round Robin, it use the HTTP Host: >>> header matching the keyserver pool. The issue with vanilla curl, is >>> however, that there is no way to manually set the SNI hostname to use, >>> and it will default to the hostname of the request. >> >> Would a separate option not be more useful for explicit testing the SNI on >> a service which can state the hostname to be pushed via the TLS handshake? > > I'm fine with both for my purposes, but using the Host: header fits in > nicely with the rest of the testing, so avoids setting yet another > option. An argument for such an approach would be for non-HTTP > transports, where there is no such header.
I'm sorry for the noise on the list. After reading a bit more in the archives and digging through documentation it seems CURLOPT_RESOLVE was implemented for my exact use case, and I'm able to use this as a workaround. -- ---------------------------- Kristian Fiskerstrand http://www.sumptuouscapital.com Twitter: @krifisk ---------------------------- "Expect the best. Prepare for the worst. Capitalize on what comes." (Zig Ziglar) ---------------------------- This email was digitally signed using the OpenPGP standard. If you want to read more about this The book: Sending Emails - The Safe Way: An introduction to OpenPGP security is available in both Amazon Kindle and Paperback format at http://www.amazon.com/dp/B006RSG1S4/ ---------------------------- Public PGP key 0xE3EDFAE3 at http://www.sumptuouscapital.com/pgp/
signature.asc
Description: OpenPGP digital signature
------------------------------------------------------------------- List admin: http://cool.haxx.se/list/listinfo/curl-library Etiquette: http://curl.haxx.se/mail/etiquette.html
