Artifactspublic-v0

curl

master
ply4 git calls31 ms292 KiB3 cachedprotocol v2
267 lines11 KiBRaw

BUGS

There are still bugs

curl and libcurl keep being developed. Adding features and changing code means that bugs sneak in, no matter how hard we try to keep them out.

Of course there are lots of bugs left. Not to mention misfeatures.

To help us make curl the stable and solid product we want it to be, we need bug reports and bug fixes.

Where to report

If you cannot fix a bug yourself and submit a fix for it, try to report an as detailed report as possible to a curl mailing list to allow one of us to have a go at a solution. You can optionally also submit your problem in curl's bug tracking system.

Please read the rest of this document below first before doing that.

If you feel you need to ask around first, find a suitable mailing list and post your questions there.

Security bugs

If you find a bug or problem in curl or libcurl that you think has a security impact, for example a bug that can put users in danger or make them vulnerable if the bug becomes public knowledge, then please report that bug using our security development process.

Security related bugs or bugs that are suspected to have a security impact, should be reported privately.

This ensures that the report reaches the curl security team so that they first can deal with the report away from the public to minimize the harm and impact it has on existing users out there who might be using the vulnerable versions.

The curl project's process for handling security related issues is documented separately.

What to report

When reporting a bug, you should include all information to help us understand what is wrong, what you expected to happen and how to repeat the bad behavior. You therefore need to tell us:

  • your operating system's name and version number

  • what version of curl you are using (curl -V is fine)

  • versions of the used libraries that libcurl is built to use

  • what URL you were working with (if possible), at least which protocol

and anything and everything else you think matters. Tell us what you expected to happen, tell us what did happen, tell us how you could make it work another way. Dig around, try out, test. Then include all the tiny bits and pieces in your report. You benefit from this yourself, as it enables us to help you quicker and more accurately.

Since curl deals with networks, it often helps us if you include a protocol debug dump with your bug report. The output you get by using the -v or --trace options.

If curl crashed, causing a core dump (in Unix), there is hardly any use to send that huge file to anyone of us. Unless we have the same system setup as you, we cannot do much with it. Instead, we ask you to get a stack trace and send that (much smaller) output to us instead.

The address and how to subscribe to the mailing lists are detailed in the MANUAL.md file.

libcurl problems

When you have written your own application with libcurl to perform transfers, it is even more important to be specific and detailed when reporting bugs.

Tell us the libcurl version and your operating system. Tell us the name and version of all relevant sub-components like for example the SSL library you are using and what name resolving your libcurl uses. If you use SFTP or SCP, the libssh2 version is relevant etc.

Showing us a real source code example repeating your problem is the best way to get our attention and it greatly increases our chances to understand your problem and to work on a fix (if we agree it truly is a problem).

Lots of problems that appear to be libcurl problems are instead abuses of the libcurl API or other malfunctions in your applications. It is advised that you run your problematic program using a memory debug tool like valgrind or similar before you post memory-related or "crashing" problems to us.

Who fixes the problems

If the problems or bugs you describe are considered to be bugs, we want to have the problems fixed.

There are no developers in the curl project that are paid to work on bugs. All developers that take on reported bugs do this on a voluntary basis. We do it out of an ambition to keep curl and libcurl excellent products and out of pride.

Please do not assume that you can lump over something to us and it then automatically gets fixed after some given time. Most often we need feedback and help to understand what you have experienced and how to repeat a problem. Then we may only be able to assist YOU to debug the problem and to track down the proper fix.

We get reports from many people every month and each report can take a considerable amount of time to really go to the bottom with.

How to get a stack trace

First, you must make sure that you compile all sources with -g and that you do not 'strip' the final executable. Try to avoid optimizing the code as well, remove -O, -O2 etc from the compiler options.

Run the program until it cores.

Run your debugger on the core file, like <debugger> curl core. <debugger> should be replaced with the name of your debugger, in most cases that is gdb, but dbx and others also occur.

When the debugger has finished loading the core file and presents you a prompt, enter where (without quotes) and press return.

The list that is presented is the stack trace. If everything worked, it is supposed to contain the chain of functions that were called when curl crashed. Include the stack trace with your detailed bug report, it helps a lot.

Bugs in libcurl bindings

There are of course bugs in libcurl bindings. You should then primarily approach the team that works on that particular binding and see what you can do to help them fix the problem.

If you suspect that the problem exists in the underlying libcurl, then please convert your program over to plain C and follow the steps outlined above.

Bugs in old versions

The curl project typically releases new versions every other month, and we fix several hundred bugs per year. For a huge table of releases, number of bug fixes and more, see: https://curl.se/docs/releases.html

The developers in the curl project do not have bandwidth or energy enough to maintain several branches or to spend much time on hunting down problems in old versions when chances are we already fixed them or at least that they have changed nature and appearance in later versions.

When you experience a problem and want to report it, you really SHOULD include the version number of the curl you are using when you experience the issue. If that version number shows us that you are using an out-of-date curl, you should also try out a modern curl version to see if the problem persists or how/if it has changed in appearance.

Even if you cannot immediately upgrade your application/system to run the latest curl version, you can most often at least run a test version or experimental build or similar, to get this confirmed or not.

At times people insist that they cannot upgrade to a modern curl version, they only "want the bug fixed". That is fine, but do not count on us spending many cycles on trying to identify which single commit, if that is even possible, that at some point in the past fixed the problem you are now experiencing.

Security wise, it is almost always a bad idea to lag behind the current curl versions by a lot. We keep discovering and reporting security problems over time see you can see in this table

Bug fixing procedure

What happens on first filing

When a new issue is posted in the issue tracker or on the mailing list, the team of developers first needs to see the report. Maybe they took the day off, maybe they are off in the woods hunting. Have patience. Allow at least a few days before expecting someone to have responded.

In the issue tracker, you can expect that some labels are set on the issue to help categorize it.

First response

If your issue/bug report was not perfect at once (and few are), chances are that someone asks follow-up questions. Which version did you use? Which options did you use? How often does the problem occur? How can we reproduce this problem? Which protocols does it involve? Or perhaps much more specific and deep diving questions. It all depends on your specific issue.

You should then respond to these follow-up questions and provide more info about the problem, so that we can help you figure it out. Or maybe you can help us figure it out. An active back-and-forth communication is important and the key for finding a cure and landing a fix.

Not reproducible

We may require further work from you who actually see or experience the problem if we cannot reproduce it and cannot understand it even after having gotten all the info we need and having studied the source code over again.

Unresponsive

If the problem have not been understood or reproduced, and there is nobody responding to follow-up questions or questions asking for clarifications or for discussing possible ways to move forward with the task, we take that as a strong suggestion that the bug is unimportant.

Unimportant issues are closed as inactive sooner or later as they cannot be fixed. The inactivity period (waiting for responses) should not be shorter than two weeks but may extend months.

Lack of time/interest

Bugs that are filed and are understood can unfortunately end up in the "nobody cares enough about it to work on it" category. Such bugs are perfectly valid problems that should get fixed but apparently are not. We try to mark such bugs as KNOWN_BUGS material after a time of inactivity and if no activity is noticed after yet some time those bugs are added to the KNOWN_BUGS document and are closed in the issue tracker.

KNOWN_BUGS

This is a list of known bugs. Bugs we know exist and that have been pointed out but that have not yet been fixed. The reasons for why they have not been fixed can involve anything really, but the primary reason is that nobody has considered these problems to be important enough to spend the necessary time and effort to have them fixed.

The KNOWN_BUGS items are always up for grabs and we love the ones who bring one of them back to life and offer solutions to them.

The KNOWN_BUGS document has a sibling document known as TODO.

TODO

Issues that are filed or reported that are not really bugs but more missing features or ideas for future improvements and so on are marked as enhancement or feature-request and get added to the TODO document and the issues are closed. We do not keep TODO items open in the issue tracker.

The TODO document is full of ideas and suggestions of what we can add or fix one day. You are always encouraged and free to grab one of those items and take up a discussion with the curl development team on how that could be implemented or provided in the project so that you can work on ticking it odd that document.

If an issue is rather a bug and not a missing feature or functionality, it is listed in KNOWN_BUGS instead.

Closing off stalled bugs

The issue and pull request trackers only hold "active" entries open (using a non-precise definition of what active actually is, but they are at least not completely dead). Those that are abandoned or in other ways dormant are closed and sometimes added to TODO and KNOWN_BUGS instead.

This way, we only have "active" issues open on GitHub. Irrelevant issues and pull requests do not distract developers or casual visitors.

1<!--
2Copyright (C) Daniel Stenberg, <daniel@haxx.se>, et al.
4SPDX-License-Identifier: curl
5-->
7# BUGS
9## There are still bugs
11curl and libcurl keep being developed. Adding features and changing code
12means that bugs sneak in, no matter how hard we try to keep them out.
14Of course there are lots of bugs left. Not to mention misfeatures.
16To help us make curl the stable and solid product we want it to be, we need
17bug reports and bug fixes.
19## Where to report
21If you cannot fix a bug yourself and submit a fix for it, try to report an as
22detailed report as possible to a curl mailing list to allow one of us to have
23a go at a solution. You can optionally also submit your problem in
24[curl's bug tracking system](https://github.com/curl/curl/issues).
26Please read the rest of this document below first before doing that.
28If you feel you need to ask around first, find a suitable
29[mailing list](https://curl.se/mail/) and post your questions there.
31## Security bugs
33If you find a bug or problem in curl or libcurl that you think has a security
34impact, for example a bug that can put users in danger or make them
35vulnerable if the bug becomes public knowledge, then please report that bug
36using our security development process.
38Security related bugs or bugs that are suspected to have a security impact,
39should be reported [privately](https://curl.se/dev/vuln-disclosure.html).
41This ensures that the report reaches the curl security team so that they first
42can deal with the report away from the public to minimize the harm and impact
43it has on existing users out there who might be using the vulnerable versions.
45The curl project's process for handling security related issues is
46[documented separately](https://curl.se/dev/secprocess.html).
48## What to report
50When reporting a bug, you should include all information to help us
51understand what is wrong, what you expected to happen and how to repeat the
52bad behavior. You therefore need to tell us:
54- your operating system's name and version number
56- what version of curl you are using (`curl -V` is fine)
58- versions of the used libraries that libcurl is built to use
60- what URL you were working with (if possible), at least which protocol
62and anything and everything else you think matters. Tell us what you expected
63to happen, tell us what did happen, tell us how you could make it work
64another way. Dig around, try out, test. Then include all the tiny bits and
65pieces in your report. You benefit from this yourself, as it enables us to
66help you quicker and more accurately.
68Since curl deals with networks, it often helps us if you include a protocol
69debug dump with your bug report. The output you get by using the `-v` or
70`--trace` options.
72If curl crashed, causing a core dump (in Unix), there is hardly any use to
73send that huge file to anyone of us. Unless we have the same system setup as
74you, we cannot do much with it. Instead, we ask you to get a stack trace and
75send that (much smaller) output to us instead.
77The address and how to subscribe to the mailing lists are detailed in the
78`MANUAL.md` file.
80## libcurl problems
82When you have written your own application with libcurl to perform transfers,
83it is even more important to be specific and detailed when reporting bugs.
85Tell us the libcurl version and your operating system. Tell us the name and
86version of all relevant sub-components like for example the SSL library
87you are using and what name resolving your libcurl uses. If you use SFTP or
88SCP, the libssh2 version is relevant etc.
90Showing us a real source code example repeating your problem is the best way
91to get our attention and it greatly increases our chances to understand your
92problem and to work on a fix (if we agree it truly is a problem).
94Lots of problems that appear to be libcurl problems are instead abuses of the
95libcurl API or other malfunctions in your applications. It is advised that you
96run your problematic program using a memory debug tool like valgrind or
97similar before you post memory-related or "crashing" problems to us.
99## Who fixes the problems
101If the problems or bugs you describe are considered to be bugs, we want to
102have the problems fixed.
104There are no developers in the curl project that are paid to work on bugs.
105All developers that take on reported bugs do this on a voluntary basis. We do
106it out of an ambition to keep curl and libcurl excellent products and out of
107pride.
109Please do not assume that you can lump over something to us and it then
110automatically gets fixed after some given time. Most often we need feedback
111and help to understand what you have experienced and how to repeat a problem.
112Then we may only be able to assist YOU to debug the problem and to track down
113the proper fix.
115We get reports from many people every month and each report can take a
116considerable amount of time to really go to the bottom with.
118## How to get a stack trace
120First, you must make sure that you compile all sources with `-g` and that you
121do not 'strip' the final executable. Try to avoid optimizing the code as well,
122remove `-O`, `-O2` etc from the compiler options.
124Run the program until it cores.
126Run your debugger on the core file, like `<debugger> curl core`. `<debugger>`
127should be replaced with the name of your debugger, in most cases that is
128`gdb`, but `dbx` and others also occur.
130When the debugger has finished loading the core file and presents you a
131prompt, enter `where` (without quotes) and press return.
133The list that is presented is the stack trace. If everything worked, it is
134supposed to contain the chain of functions that were called when curl
135crashed. Include the stack trace with your detailed bug report, it helps a
136lot.
138## Bugs in libcurl bindings
140There are of course bugs in libcurl bindings. You should then primarily
141approach the team that works on that particular binding and see what you can
142do to help them fix the problem.
144If you suspect that the problem exists in the underlying libcurl, then please
145convert your program over to plain C and follow the steps outlined above.
147## Bugs in old versions
149The curl project typically releases new versions every other month, and we
150fix several hundred bugs per year. For a huge table of releases, number of
151bug fixes and more, see: https://curl.se/docs/releases.html
153The developers in the curl project do not have bandwidth or energy enough to
154maintain several branches or to spend much time on hunting down problems in
155old versions when chances are we already fixed them or at least that they have
156changed nature and appearance in later versions.
158When you experience a problem and want to report it, you really SHOULD
159include the version number of the curl you are using when you experience the
160issue. If that version number shows us that you are using an out-of-date curl,
161you should also try out a modern curl version to see if the problem persists
162or how/if it has changed in appearance.
164Even if you cannot immediately upgrade your application/system to run the
165latest curl version, you can most often at least run a test version or
166experimental build or similar, to get this confirmed or not.
168At times people insist that they cannot upgrade to a modern curl version, they
169only "want the bug fixed". That is fine, but do not count on us spending many
170cycles on trying to identify which single commit, if that is even possible,
171that at some point in the past fixed the problem you are now experiencing.
173Security wise, it is almost always a bad idea to lag behind the current curl
174versions by a lot. We keep discovering and reporting security problems
175over time see you can see in
176[this table](https://curl.se/docs/vulnerabilities.html)
178# Bug fixing procedure
180## What happens on first filing
182When a new issue is posted in the issue tracker or on the mailing list, the
183team of developers first needs to see the report. Maybe they took the day off,
184maybe they are off in the woods hunting. Have patience. Allow at least a few
185days before expecting someone to have responded.
187In the issue tracker, you can expect that some labels are set on the issue to
188help categorize it.
190## First response
192If your issue/bug report was not perfect at once (and few are), chances are
193that someone asks follow-up questions. Which version did you use? Which
194options did you use? How often does the problem occur? How can we reproduce
195this problem? Which protocols does it involve? Or perhaps much more specific
196and deep diving questions. It all depends on your specific issue.
198You should then respond to these follow-up questions and provide more info
199about the problem, so that we can help you figure it out. Or maybe you can
200help us figure it out. An active back-and-forth communication is important
201and the key for finding a cure and landing a fix.
203## Not reproducible
205We may require further work from you who actually see or experience the
206problem if we cannot reproduce it and cannot understand it even after having
207gotten all the info we need and having studied the source code over again.
209## Unresponsive
211If the problem have not been understood or reproduced, and there is nobody
212responding to follow-up questions or questions asking for clarifications or
213for discussing possible ways to move forward with the task, we take that as a
214strong suggestion that the bug is unimportant.
216Unimportant issues are closed as inactive sooner or later as they cannot be
217fixed. The inactivity period (waiting for responses) should not be shorter
218than two weeks but may extend months.
220## Lack of time/interest
222Bugs that are filed and are understood can unfortunately end up in the
223"nobody cares enough about it to work on it" category. Such bugs are
224perfectly valid problems that *should* get fixed but apparently are not. We
225try to mark such bugs as `KNOWN_BUGS material` after a time of inactivity and
226if no activity is noticed after yet some time those bugs are added to the
227`KNOWN_BUGS` document and are closed in the issue tracker.
229## `KNOWN_BUGS`
231This is a list of known bugs. Bugs we know exist and that have been pointed
232out but that have not yet been fixed. The reasons for why they have not been
233fixed can involve anything really, but the primary reason is that nobody has
234considered these problems to be important enough to spend the necessary time
235and effort to have them fixed.
237The `KNOWN_BUGS` items are always up for grabs and we love the ones who bring
238one of them back to life and offer solutions to them.
240The `KNOWN_BUGS` document has a sibling document known as `TODO`.
242## `TODO`
244Issues that are filed or reported that are not really bugs but more missing
245features or ideas for future improvements and so on are marked as
246*enhancement* or *feature-request* and get added to the `TODO` document and
247the issues are closed. We do not keep TODO items open in the issue tracker.
249The `TODO` document is full of ideas and suggestions of what we can add or
250fix one day. You are always encouraged and free to grab one of those items and
251take up a discussion with the curl development team on how that could be
252implemented or provided in the project so that you can work on ticking it odd
253that document.
255If an issue is rather a bug and not a missing feature or functionality, it is
256listed in `KNOWN_BUGS` instead.
258## Closing off stalled bugs
260The [issue and pull request trackers](https://github.com/curl/curl) only hold
261"active" entries open (using a non-precise definition of what active actually
262is, but they are at least not completely dead). Those that are abandoned or
263in other ways dormant are closed and sometimes added to `TODO` and
264`KNOWN_BUGS` instead.
266This way, we only have "active" issues open on GitHub. Irrelevant issues and
267pull requests do not distract developers or casual visitors.
Diagnostics4 git calls · 31 ms
CallStatusSizeTime031 ms
discover200152 B2 ms
git.upload-pack discover
http.response.status_code=200
git.upstream.cf_ray=-
git.upstream.phase=ls-refs
git.upstream.dur_ms=2
git.response.bytes=152
git.server.agent=gitty/1.0
git.server.object_format=sha1
git.server.caps=agent ls-refs fetch object-format
git.server.fetch=shallow filter sideband-all
git.protocol.version=2
git.pkt.frames=8
git.pkt.data=6
git.pkt.flush=2
git.pkt.delim=0
git.pkt.bytes=152
git.pkt.payload.max=34
ls-refs200149 B · hit2 ms
git.upload-pack ls-refs
http.response.status_code=200
git.upstream.cf_ray=-
git.upstream.phase=ls-refs
git.upstream.dur_ms=2
git.response.bytes=149
git.response.cache=HIT
git.response.duration_ms=2
git.protocol.version=2
git.pkt.frames=3
git.pkt.data=2
git.pkt.flush=1
git.pkt.delim=0
git.pkt.bytes=149
git.pkt.payload.max=78
git.ls_refs.count=2
git.ls_refs.head=refs/heads/master
fetchblob:none · deepen 10200287 KiB · hit3 ms
git.upload-pack fetch
http.response.status_code=200
git.upstream.cf_ray=-
git.upstream.phase=fetch
git.upstream.dur_ms=3
git.response.bytes=293470
git.response.cache=HIT
git.response.duration_ms=3
git.fetch.filter=blob:none
git.fetch.filter.requested=tree:0
git.fetch.filter.fallback=blob:none
git.fetch.filter.learned=false
git.fetch.wants=31c911efe5652725e930f4d2e60c9060e5f6646d
git.fetch.haves.count=0
git.fetch.deepen=10
git.fetch.thin_pack=false
git.fetch.ofs_delta=true
git.protocol.version=2
git.pkt.frames=10
git.pkt.data=8
git.pkt.flush=1
git.pkt.delim=1
git.pkt.bytes=293470
git.pkt.payload.max=65516
git.sideband.band1.bytes=293354
git.sideband.band2.bytes=0
git.sideband.band3.bytes=0
git.pack.objects=87
git.pack.bytes=293354
git.pack.ofs_delta=0
git.pack.ref_delta=1
git.pack.chain.max=1
git.pack.trailer=6a646bcda6740bab42e321b51998b52ea15146c0
git.pack.full=86
Open pack map
fetch2005.1 KiB · hit26 ms
git.upload-pack fetch
http.response.status_code=200
git.upstream.cf_ray=-
git.upstream.phase=fetch
git.upstream.dur_ms=25
git.response.bytes=5203
git.response.cache=HIT
git.response.duration_ms=26
git.fetch.wants=5f3704771ba9406d63f4b16ae9d5863ce2b1265a
git.fetch.haves.count=0
git.fetch.deepen=0
git.fetch.thin_pack=false
git.fetch.ofs_delta=true
git.protocol.version=2
git.pkt.frames=3
git.pkt.data=2
git.pkt.flush=1
git.pkt.delim=0
git.pkt.bytes=5203
git.pkt.payload.max=5182
git.sideband.band1.bytes=5181
git.sideband.band2.bytes=0
git.sideband.band3.bytes=0

Each row is one HTTP round trip ply made to the git server for this page, on one timeline. discover asks what the server speaks, ls-refs lists branch tips, fetch brings objects by id. A hit was served by Workers Cache. Tap a row for its wire details.

Remote
https://5ad2236b39de4c8bd8f6270ea63f3ea9.artifacts.cloudflare.net/git/public-v0/curl.git
Ref
refs/heads/master
Commit
31c911efe5652725e930f4d2e60c9060e5f6646d
cf-ray
a5e19c334cbc3cd0
Request
24c9ae9c…
Protocol
v2 · sha1
Agent
gitty/1.0
Filter
advertised
Fetch
shallow filter sideband-all
Capabilities
agent ls-refs fetch object-format