#
86d33001 |
| 31-Mar-2024 |
Daniel Stenberg |
reuse: add copyright + license info to individual docs/*.md files Instead of use 'docs/*.md' in dep5. For clarity and avoiding a wide- matching wildcard. + Remove mention of old
reuse: add copyright + license info to individual docs/*.md files Instead of use 'docs/*.md' in dep5. For clarity and avoiding a wide- matching wildcard. + Remove mention of old files from .reuse/dep5 + add info to .github/dependabot.yml + make scripts/copyright.pl warn on non-matching patterns Closes #13245
show more ...
|
#
dc3eb678 |
| 06-Feb-2024 |
Daniel Stenberg |
badwords: use hostname, not host name and username, filename - consistently. Fixed the patterns in badwords.txt to catch these. Closes #12888
|
#
e5000e79 |
| 23-Jan-2024 |
Daniel Stenberg |
GHA: add a job scanning for "bad words" in markdown This means words, phrases or things we have decided not to use - words that are spelled right according to the dictionary but we want
GHA: add a job scanning for "bad words" in markdown This means words, phrases or things we have decided not to use - words that are spelled right according to the dictionary but we want to avoid. In the name of consistency and better documentation. Closes #12764
show more ...
|
#
14612e5f |
| 22-Nov-2023 |
Daniel Stenberg |
FEATURES: update the URL phrasing The URL is length limited since a while back so "no limit" simply is not true anymore. Mention the URL RFC standard used instead. Closes #12383
|
#
7c8bae0d |
| 29-Jul-2023 |
Daniel Stenberg |
nss: remove support for this TLS library Closes #11459
|
#
22c92a6d |
| 25-Jun-2023 |
Daniel Stenberg |
docs: use a space after RFC when spelling out RFC numbers Closes #11382
|
#
fd1ce3d4 |
| 20-Sep-2022 |
Daniel Stenberg |
docs: spellfixes Pointed by the new CI job
|
#
93fe8a04 |
| 20-May-2022 |
Daniel Gustafsson |
FEATURES: remove yassl as TLS library for NTLM yassl was added in commit 9d904ee41b880b but is no longer available and is thus not a library to use for NTLM. This aligns the FEATURES
FEATURES: remove yassl as TLS library for NTLM yassl was added in commit 9d904ee41b880b but is no longer available and is thus not a library to use for NTLM. This aligns the FEATURES doc with the FAQ. Closes: #8886 Reviewed-by: Daniel Stenberg <daniel@haxx.se>
show more ...
|
#
3022c5a9 |
| 20-May-2022 |
Daniel Gustafsson |
FEATURES: reorder footnotes The empty left-behind footnote confused the website rendering into creating a nested emoty list, making the resulting page look quite odd. Remove and re-
FEATURES: reorder footnotes The empty left-behind footnote confused the website rendering into creating a nested emoty list, making the resulting page look quite odd. Remove and re-order the remaining ones to avoid a gap in the sequence. Closes: #8886 Reviewed-by: Daniel Stenberg <daniel@haxx.se>
show more ...
|
#
94ac2ca7 |
| 21-Apr-2022 |
Kushal Das |
docs: updates spellings with full words Closes #8730
|
#
3a4182d4 |
| 29-Mar-2022 |
Daniel Stenberg |
docs: lots of minor language polish Mostly based on recent language decisions from "everything curl": - remove contractions (isn't => is not) - *an* HTTP (consistency) - run
docs: lots of minor language polish Mostly based on recent language decisions from "everything curl": - remove contractions (isn't => is not) - *an* HTTP (consistency) - runtime (no hyphen) - backend (no hyphen) - URL is uppercase Closes #8646
show more ...
|
#
09c80742 |
| 30-Jan-2022 |
Jan-Piet Mens |
docs: capitalize the name 'Netscape' Closes https://github.com/curl/curl/pull/8354
|
#
7a92f865 |
| 17-Dec-2021 |
Daniel Stenberg |
misc: s/e-mail/email Consistency is king. Following the lead in everything curl. Closes #8159
|
#
265b14d6 |
| 01-Jun-2021 |
Daniel Stenberg |
metalink: remove Warning: this will make existing curl command lines that use metalink to stop working. Reasons for removal: 1. We've found several security problems an
metalink: remove Warning: this will make existing curl command lines that use metalink to stop working. Reasons for removal: 1. We've found several security problems and issues involving the metalink support in curl. The issues are not detailed here. When working on those, it become apparent to the team that several of the problems are due to the system design, metalink library API and what the metalink RFC says. They are very hard to fix on the curl side only. 2. The metalink usage with curl was only very briefly documented and was not following the "normal" curl usage pattern in several ways, making it surprising and non-intuitive which could lead to further security issues. 3. The metalink library was last updated 6 years ago and wasn't so active the years before that either. An unmaintained library means there's a security problem waiting to happen. This is probably reason enough. 4. Metalink requires an XML parsing library, which is complex code (even the smaller alternatives) and to this day often gets security updates. 5. Metalink is not a widely used curl feature. In the 2020 curl user survey, only 1.4% of the responders said that they'd are using it. In 2021 that number was 1.2%. Searching the web also show very few traces of it being used, even with other tools. 6. The torrent format and associated technology clearly won for downloading large files from multiple sources in parallel. Cloes #7176
show more ...
|
Revision tags: curl-7_76_1, curl-7_76_0, curl-7_75_0, curl-7_74_0 |
|
#
621e147c |
| 13-Oct-2020 |
Daniel Stenberg |
docs/FEATURE: convert to markdown ... and clean it up a bit. Closes #6067
|