delta/curl.git/src/tool_metalink.c, branch bagder/disabled-proxy-options github.com: bagder/curl.git build: fix Codacy/CppCheck warnings 2019-04-11T19:08:44+00:00 Marcel Raad Marcel.Raad@teamviewer.com 2019-04-05T17:57:29+00:00 d1b5cf830bfe169745721b21245d2217d2c2453e - remove unused variables - declare conditionally used variables conditionally - suppress unused variable warnings in the CMake tests - remove dead variable stores - consistently use WIN32 macro to detect Windows Closes https://github.com/curl/curl/pull/3739 
- remove unused variables
- declare conditionally used variables conditionally
- suppress unused variable warnings in the CMake tests
- remove dead variable stores
- consistently use WIN32 macro to detect Windows

Closes https://github.com/curl/curl/pull/3739
GCC: silence -Wcast-function-type uniformly 2018-08-11T17:19:04+00:00 Marcel Raad Marcel.Raad@teamviewer.com 2018-08-10T15:32:01+00:00 f31911a8002d3c9de109f5352328d8b6fbf035c2 Pointed-out-by: Rikard Falkeborn Closes https://github.com/curl/curl/pull/2860 
Pointed-out-by: Rikard Falkeborn
Closes https://github.com/curl/curl/pull/2860
checksrc: make sure sizeof() is used *with* parentheses 2018-05-21T21:21:47+00:00 Daniel Stenberg daniel@haxx.se 2018-05-11T21:40:58+00:00 cb529b713f4882ac65a074ae8d87faa41d19168e ... and unify the source code to adhere. Closes #2563 
... and unify the source code to adhere.

Closes #2563
gcc: disable picky gcc-8 function pointer warnings in two places 2018-05-14T21:09:51+00:00 Daniel Stenberg daniel@haxx.se 2018-05-14T07:55:34+00:00 c0f704dbae32c6e1c9bb5325d6317fca67de04f5 Reported-by: Rikard Falkeborn Bug: #2560 Closes #2569 
Reported-by: Rikard Falkeborn
Bug: #2560
Closes #2569
cleanup: misc typos in strings and comments 2018-03-16T10:08:31+00:00 luz.paz luzpaz@users.noreply.github.com 2018-03-16T02:51:03+00:00 236402fc2d02068b2ce3656200031ced2fa3c8b1 Found via `codespell` Closes #2389 
Found via `codespell`

Closes #2389
metalink: fix memory-leak and NULL pointer dereference 2017-11-24T12:30:38+00:00 Daniel Stenberg daniel@haxx.se 2017-11-24T08:02:54+00:00 d6ec96f7ffc5e8ee264d206634d3ec146794b80b Reported by scan-build Closes #2109 
Reported by scan-build

Closes #2109
metalink: fix NSS issue in MultiSSL builds 2017-09-22T19:01:28+00:00 Viktor Szakats vszakats@users.noreply.github.com 2017-09-12T18:14:00+00:00 de47158934075322cb8fd0e681ddb7d6e50b40a7 In MultiSSL mode (i.e. when more than one SSL backend is compiled in), we cannot use the compile time flag `USE_NSS` as indicator that the NSS backend is in use. As far as Metalink is concerned, the SSL backend is only used for MD5, SHA-1 and SHA-256 calculations, therefore one of the available SSL backends is selected at compile time, in a strict order of preference. Let's introduce a new `HAVE_NSS_CONTEXT` constant that can be used to determine whether the SSL backend used for Metalink is the NSS backend, and use that to guard the code that wants to de-initialize the NSS-specific data structure. Ref: https://github.com/curl/curl/pull/1848 
In MultiSSL mode (i.e. when more than one SSL backend is compiled
in), we cannot use the compile time flag `USE_NSS` as indicator that
the NSS backend is in use. As far as Metalink is concerned, the SSL
backend is only used for MD5, SHA-1 and SHA-256 calculations,
therefore one of the available SSL backends is selected at compile
time, in a strict order of preference.

Let's introduce a new `HAVE_NSS_CONTEXT` constant that can be used
to determine whether the SSL backend used for Metalink is the NSS
backend, and use that to guard the code that wants to de-initialize
the NSS-specific data structure.

Ref: https://github.com/curl/curl/pull/1848
code style: use spaces around pluses 2017-09-11T07:29:50+00:00 Daniel Stenberg daniel@haxx.se 2017-09-09T21:55:08+00:00 e5743f08e7efb387bb39c0dc28f36838ece3bc1e 






metalink: allow compiling with multiple SSL backends
2017-08-28T12:56:59+00:00

Johannes Schindelin
johannes.schindelin@gmx.de

2017-08-18T05:53:33+00:00

b180a273fab64b601e7f44a36a0ec8bd5363e8e1

Previously, the code assumed that at most one of the SSL backends would
be compiled in, emulating OpenSSL's functions if the configured backend
was not OpenSSL itself.

However, now we allow building with multiple SSL backends and choosing
one at runtime. Therefore, metalink needs to be adjusted to handle this
scenario, too.

Signed-off-by: Johannes Schindelin <johannes.schindelin@gmx.de>





Previously, the code assumed that at most one of the SSL backends would
be compiled in, emulating OpenSSL's functions if the configured backend
was not OpenSSL itself.

However, now we allow building with multiple SSL backends and choosing
one at runtime. Therefore, metalink needs to be adjusted to handle this
scenario, too.

Signed-off-by: Johannes Schindelin <johannes.schindelin@gmx.de>







metalink: adjust source code style
2017-08-18T06:46:52+00:00

Johannes Schindelin
johannes.schindelin@gmx.de

2017-08-18T05:58:16+00:00

1f39245dc8da51dcd81e5aed2fdd5d1f7ebbe23b

Signed-off-by: Johannes Schindelin <johannes.schindelin@gmx.de>





Signed-off-by: Johannes Schindelin <johannes.schindelin@gmx.de>