サクサク読めて、アプリ限定の機能も多数!
トップへ戻る
iPhone 16
daniel.haxx.se
— “Have you ever detected anyone trying to add a backdoor to curl?” — “Have you ever been pressured by an organization or a person to add suspicious code to curl that you wouldn’t otherwise accept?” — “If a crime syndicate would kidnap your family to force you to comply, what backdoor would you be be able to insert into curl that is the least likely to get detected?” (The less grim version of this
– Sorry, you’re not allowed entry to the US on your ESTA. The lady who delivered this message to me this early Monday morning, worked behind the check-in counter at the Arlanda airport. I was there, trying to check-in to my two-leg trip to San Francisco to the Mozilla “all hands” meeting of the summer of 2017. My chance for a while ahead to meet up with colleagues from all around the world. This s
One of the least favorite habits of curl during all these years, I’ve been told, is when users forget to instruct the command line tool where to store the downloaded file and as a direct consequence, curl instead sends a lot of binary “gunk” to the terminal. The end result of that is at best just a busload of weird-looking characters on the screen, but with just a little bit of bad luck it can als
Today I landed yet another small change to libcurl internals that further reduces the number of small mallocs we do. This time the generic linked list functions got converted to become malloc-less (the way linked list functions should behave, really). Instrument mallocs I started out my quest a few weeks ago by instrumenting our memory allocations. This is easy since we have our own memory debug a
I posted curl is C a few days ago and it raced on hacker news, reddit and elsewhere and got well over a thousand comments in those forums alone. The blog post has been read more than 130,000 times so far. Addendum a few days later Many commenters of my curl is C post struck down on my claim that most of our security flaws aren’t due to curl being written in C. It turned out into some sort of CVE c
For some reason, this post got picked up again and is debated today in 2021, almost 4 years since I wrote it. Some things have changed in the mean time and I might’ve phrased a few things differently if I had written this today. But still, what’s here below is what I wrote back then. Enjoy! Every once in a while someone suggests to me that curl and libcurl would do better if rewritten in a “safe l
Following up on the problem with our current lack of a universal URL standard that I blogged about in May 2016: My URL isn’t your URL. I want a single, unified URL standard that we would all stand behind, support and adhere to. What triggers me this time, is yet another issue. A friendly curl user sent me this URL: http://user@example.com:80@daniel.haxx.se … and pasting this URL into different too
bittorrent vs HTTP Here's a comparison between the use of bittorrent vs HTTP for data transfers. Basic Facts Bittorrent is a way for a client to figure out what peers that have a piece of a particular file so that it can get pieces from those machines instead of getting the entire thing from a single (central) place. Transfer Speed With HTTP a file is presented in a single stream by the HTTP serve
I am the founder and lead developer of cURL and libcurl. An internet protocol geek, an open source person and a developer. I've been programming for fun and profit since 1985. You'll find lots of info about my various Open Source projects on these web pages and on my GitHub profile. My name appears in products. I participate within the IETF, primarily in the HTTPbis and QUIC working groups. I spea
Modern cars have fancy infotainment setups, big screens and all sorts of computers with networked functionality built-in. Part of that fanciness is increasingly often a curl install. curl is a part of the standard GenIVI and Tizen offers for cars and is used in lots of other independent software installs too. This usually affects my every day very little. Sure I’m thrilled over hundreds of million
When Mac OS X first launched they did so without an existing poll function. They later added poll() in Mac OS X 10.3, but we quickly discovered that it was broken (it returned a non-zero value when asked to wait for nothing) so in the curl project we added a check in configure for that and subsequently avoided using poll() in all OS X versions to and including Mac OS 10.8 (Darwin 12). The code wou
Section 9.1.1 in RFC7540 explains how HTTP/2 clients can reuse connections. This is my lengthy way of explaining how this works in reality. Many connections in HTTP/1 With HTTP/1.1, browsers are typically using 6 connections per origin (host name + port). They do this to overcome the problems in HTTP/1 and how it uses TCP – as each connection will do a fair amount of waiting. Plus each connection
$ curl ‐‐http2 https://daniel.haxx.se/ curl: (1) Unsupported protocol curl on mac curl has been shipped by default on Mac OS X since many years – I actually couldn’t even manage to figure out exactly how many. It is built and bundled with the operating system by Apple itself and on Apple’s own terms and even though I’m the main curl developer I’ve never discussed this with them or even been asked
The interesting Google transfer protocol that is known as QUIC is being passed through the IETF grinding machines to hopefully end up with a proper “spec” that has been reviewed and agreed to by many peers and that will end up being a protocol that is thoroughly documented with a lot of protocol people’s consensus. Follow the IETF QUIC mailing list for all the action. I’d like us to join the fun S
There is no websockets for HTTP/2. By this, I mean that there’s no way to negotiate or upgrade a connection to websockets over HTTP/2 like there is for HTTP/1.1 as expressed by RFC 6455. That spec details how a client can use Upgrade: in a HTTP/1.1 request to switch that connection into a websockets connection. Note that websockets is not part of the HTTP/1 spec, it just uses a HTTP/1 protocol det
The original logo for the curl project was created in 1998 by Henrik Hellerstedt. When we started version controlling the web site contents in June 2001 it had already been revised slightly and it looked like this I subsequently did the slightly refreshed version that’s been visible on the site since early 2003 which sort of emphasized the look by squeezing the letters together. The general “cURL”
When I started the precursor to the curl project, httpget, back in 1996, I wrote my first URL parser. Back then, the universal address was still called URL: Uniform Resource Locators. That spec was published by the IETF in 1994. The term “URL” was then used as source for inspiration when naming the tool and project curl. The term URL was later effectively changed to become URI, Uniform Resource Id
Followers of this blog know that I’ve dabbled with HTTP/2 stuff for quite some time, and curl got its initial support for the new protocol version already in September 2013. curl shipped “proper” HTTP/2 support as it looks in the final specification both for the command line tool and the libcurl library before any browsers did in their release versions. (Firefox was the first browser to ship HTTP/
We just shipped our 150th public release of curl. On December 2, 2015. curl 7.46.0 One hundred and fifty public releases done during almost 18 years makes a little more than 8 releases per year on average. In mid November 2015 we also surpassed 20,000 commits in the git source code repository. With the constant and never-ending release train concept of just another release every 8 weeks that we’re
During October 2015 the curl web site sent out 1127 gigabytes of data. This was the first time we crossed the terabyte limit within a single month. Looking at the stats a little closer, I noticed that in July 2015 a particular single package started to get very popular. The exact URL was http://curl.haxx.se/gknw.net/7.40.0/dist-w32/curl-7.40.0-devel-mingw32.zip Curious. In October it alone was dow
Tuesday October 13th 2015 I co-presented a talk at the Velocity conference in NYC together with Ragnar Lönn of Loadimpact. Ragnar is a friend of mine and another Swede. The presentation was split up in two parts, in which I laid out the foundations of HTTP/2 in the first part, and Ragnar then presented the results of his performance study in the second part. I think an interesting take away from t
MOAR DOX! Whenever we ask curl users what they lack in our project and what we should improve, the response is always clear: documentation. Here are the most common curl command line options when doing HTTP operations. This is the web page rendered as an image, click it to get to the web version. The source for the document/image is on github. As always, you can help improving it. Update: see the
So we started today. I won’t get into any live details or quotes from the day since it has all been informal and we’ve all agreed to not expose snippets from here without checking properly first. There will be a detailed report put together from this event afterwards. The most critical peace of information is however how we must not walk on the red parts of the sidewalks here in Münster, as that’s
If I had only recorded the sound, you would have flamed me for that since it would not be easy to know which slides that go with which talk. And people interrupting or asking would be hard to hear and make the talk one-sided. And chances are the general sound quality would’ve sucked. How hard would it be to record the sound properly? If I had recorded the talk using a basic video camera from a dis
The protocol HTTP/2 as defined in the draft-17 was approved by the IESG and is being implemented and deployed widely on the Internet today, even before it has turned up as an actual RFC. Back in February, already upwards 5% or maybe even more of the web traffic was using HTTP/2. My prediction: We’ll see >10% usage by the end of the year, possibly as much as 20-30% a little depending on how fast so
Today we celebrate the fact that it is exactly 17 years since the first public release of curl. I have always been the lead developer and maintainer of the project. When I released that first version in the spring of 1998, we had only a handful of users and a handful of contributors. curl was just a little tool and we were still a few years out before libcurl would become a thing of its own. The t
I’ve written the http2 explained document and I’ve done several talks about HTTP/2. I’ve gotten a lot of questions about TLS in association with HTTP/2 due to this, and I want to address some of them here. TLS is not mandatory In the HTTP/2 specification that has been approved and that is about to become an official RFC any day now, there is no language that mandates the use of TLS for securing th
http2 explained Background, the protocol, the implementations and the future http://daniel.haxx.se/http2/ by Daniel Stenberg Table of Contents 1.Background.................................................................................................................................................................... 4 1.1.Author....................................................................
http2 Background, the protocol, the implementations and the future http.//daniel.haxx.se/http2/ by Daniel Stenberg 1 Table of Contents 1.Background.................................................................................................................................................................... 4 1.1.Author............................................................................
次のページ
このページを最初にブックマークしてみませんか?
『Daniel Stenberg - daniel.haxx.se』の新着エントリーを見る
j次のブックマーク
k前のブックマーク
lあとで読む
eコメント一覧を開く
oページを開く