On Mon, Jun 04, 2018 at 04:07:56PM +, Jonathan C. wrote:
> I really cannot grasp all this M$ is evil and will doom GH mantra.
+1.
- Dmitri.
---
Unsubscribe: https://cool.haxx.se/list/listinfo/curl-library
Etiquette: https://c
On Wed, Apr 25, 2018 at 01:10:17PM +0200, Rainer Canavan wrote:
> Curl_http_readwrite_headers() explicitly checks if
> data->set.str[STRING_ENCODING] was set (i.e. an Accept-Encoding header
> was sent), and therefore disables compression.
>
> I would simply remove that check for STRING_ENCODING. O
On Tue, Oct 31, 2017 at 09:22:39AM +, Lucas Pardue via curl-library wrote:
> Some nice discussion going on, just wanted to bump the visibility of
> the curl QUIC wiki page. There's some topics that could be enhanced
> with information if the work is to begin. It might also be nice to
> capture
On Mon, Oct 30, 2017 at 10:55:06PM -0400, Dmitri Tikhonov wrote:
> On Mon, Oct 30, 2017 at 10:39:14PM +0100, Daniel Stenberg wrote:
> > but I too don't have a lot of extra to bring to the table on this
> > right now for me it is primarily because I haven't properly read
On Tue, Oct 31, 2017 at 12:42:44PM +0100, Gisle Vanem via curl-library wrote:
> Lucas Pardue wrote:
> >
> >Whoops, the page is located at https://github.com/curl/curl/wiki/QUIC.
>
> That lists:
> ngtcp2 (C-library)
> MozQuic (C++ library)
> quicly (C-library)
> LiteSpeed QUIC client (C-lib
On Mon, Oct 30, 2017 at 10:39:14PM +0100, Daniel Stenberg wrote:
> On Mon, 30 Oct 2017, Dmitri Tikhonov wrote:
>
> >This point is obvious, but it bears repeating: all but one (file:)
> >protocol that curl supports use TCP. It may mean that some of the curl
> >gut
Hello,
I have been thinking about how to add QUIC support to curl; in
particular, how to add QUIC support to curl using LSQUIC Client
Library [1]. I spent some time reading curl code and documentation
and I have a few high-level ideas that I'd like to present -- hopefully,
to get some feedback.
