curl/tests/libtest/lib541.c

Ignoring revisions in .git-blame-ignore-revs. Click here to bypass and see the normal blame view.

124 lines
3.2 KiB
C
Raw Permalink Normal View History

/***************************************************************************
* _ _ ____ _
* Project ___| | | | _ \| |
* / __| | | | |_) | |
* | (__| |_| | _ <| |___
* \___|\___/|_| \_\_____|
*
* Copyright (C) Daniel Stenberg, <daniel@haxx.se>, et al.
*
* This software is licensed as described in the file COPYING, which
* you should have received as part of this distribution. The terms
2020-11-04 14:02:01 +01:00
* are also available at https://curl.se/docs/copyright.html.
*
* You may opt to use, copy, modify, merge, publish, distribute and/or sell
* copies of the Software, and permit persons to whom the Software is
* furnished to do so, under the terms of the COPYING file.
*
* This software is distributed on an "AS IS" basis, WITHOUT WARRANTY OF ANY
* KIND, either express or implied.
*
* SPDX-License-Identifier: curl
*
***************************************************************************/
#include "test.h"
#ifdef HAVE_FCNTL_H
#include <fcntl.h>
#endif
#include "memdebug.h"
2008-09-20 04:26:55 +00:00
/*
* Two FTP uploads, the second with no content sent.
*/
CURLcode test(char *URL)
{
CURL *curl;
CURLcode res = CURLE_OK;
FILE *hd_src;
int hd;
struct_stat file_info;
if(!libtest_arg2) {
fprintf(stderr, "Usage: <url> <file-to-upload>\n");
return TEST_ERR_USAGE;
}
hd_src = fopen(libtest_arg2, "rb");
if(!hd_src) {
tests: reformat error messages to avoid tripping MSBuild Change the format of error messages sent to stderr from tests and test servers. As a workaround to avoid triggering Visual Studio's MSBuild tool's built-in regexp matcher, and making it mark builds failed for reasons we don't want them to hard fail. Roughly, the pattern to avoid is the word "error" (case-insensitive) in the same line with a colon `:`. It affected GHA/windows MSVC CI jobs, causing flakiness: ``` CUSTOMBUILD : fopen() failed with error : 13 Permission denied [D:\a\curl\curl\bld\tests\test-ci.vcxproj] Error opening file: log/4/smtp_sockfilt.log [...] CUSTOMBUILD : fopen() failed with error : 13 Permission denied [D:\a\curl\curl\bld\tests\test-ci.vcxproj] Error opening file: log/8/imap_sockfilt.log Msg not logged: 00:18:10.656000 > 178 bytes data, server => client [...] TESTDONE: 1629 tests out of 1634 reported OK: 99% Building Custom Rule D:/a/curl/curl/tests/CMakeLists.txt C:\Program Files\Microsoft Visual Studio\2022\Enterprise\MSBuild\Microsoft\VC\v170\Microsoft.CppCommon.targets(254,5): error MSB8066: Custom build for 'D:\a\curl\curl\bld\CMakeFiles\621f80ddbb0fa48179f056ca77842ff0\test-ci.rule;D:\a\curl\curl\tests\CMakeLists.txt' exited with code -1. [D:\a\curl\curl\bld\tests\test-ci.vcxproj] Error: Process completed with exit code 1. ``` Ref: https://github.com/curl/curl/actions/runs/13643149623/job/38137076210?pr=16490#step:14:3125 Ref: https://github.com/curl/curl/actions/runs/13688765792/job/38277961720?pr=16582#step:14:1717 The `IgnoreStandardErrorWarningFormat="true"` MSBuild Exec option controls this behavior: https://learn.microsoft.com/visualstudio/msbuild/exec-task#parameters I couldn't figure out a way to apply it to CMake builds. MSBuid pattern matching rules: https://github.com/dotnet/msbuild/blob/353c0f3d37957cc98bfa6a76b568d70d12193fc3/src/Shared/CanonicalError.cs https://learn.microsoft.com/visualstudio/msbuild/msbuild-diagnostic-format-for-tasks Note: There may be further error messages output from runtests scripts, that use this format, which are not explicitly fatal. They may need future fixes. Thanks-to: Dion Williams Ref: https://github.com/curl/curl/discussions/14854#discussioncomment-12382190 Ref: https://github.com/curl/curl/discussions/14854#discussioncomment-12395224 Closes #16583
2025-03-06 04:13:23 +01:00
fprintf(stderr, "fopen failed with error (%d) %s\n",
errno, strerror(errno));
tests: reformat error messages to avoid tripping MSBuild Change the format of error messages sent to stderr from tests and test servers. As a workaround to avoid triggering Visual Studio's MSBuild tool's built-in regexp matcher, and making it mark builds failed for reasons we don't want them to hard fail. Roughly, the pattern to avoid is the word "error" (case-insensitive) in the same line with a colon `:`. It affected GHA/windows MSVC CI jobs, causing flakiness: ``` CUSTOMBUILD : fopen() failed with error : 13 Permission denied [D:\a\curl\curl\bld\tests\test-ci.vcxproj] Error opening file: log/4/smtp_sockfilt.log [...] CUSTOMBUILD : fopen() failed with error : 13 Permission denied [D:\a\curl\curl\bld\tests\test-ci.vcxproj] Error opening file: log/8/imap_sockfilt.log Msg not logged: 00:18:10.656000 > 178 bytes data, server => client [...] TESTDONE: 1629 tests out of 1634 reported OK: 99% Building Custom Rule D:/a/curl/curl/tests/CMakeLists.txt C:\Program Files\Microsoft Visual Studio\2022\Enterprise\MSBuild\Microsoft\VC\v170\Microsoft.CppCommon.targets(254,5): error MSB8066: Custom build for 'D:\a\curl\curl\bld\CMakeFiles\621f80ddbb0fa48179f056ca77842ff0\test-ci.rule;D:\a\curl\curl\tests\CMakeLists.txt' exited with code -1. [D:\a\curl\curl\bld\tests\test-ci.vcxproj] Error: Process completed with exit code 1. ``` Ref: https://github.com/curl/curl/actions/runs/13643149623/job/38137076210?pr=16490#step:14:3125 Ref: https://github.com/curl/curl/actions/runs/13688765792/job/38277961720?pr=16582#step:14:1717 The `IgnoreStandardErrorWarningFormat="true"` MSBuild Exec option controls this behavior: https://learn.microsoft.com/visualstudio/msbuild/exec-task#parameters I couldn't figure out a way to apply it to CMake builds. MSBuid pattern matching rules: https://github.com/dotnet/msbuild/blob/353c0f3d37957cc98bfa6a76b568d70d12193fc3/src/Shared/CanonicalError.cs https://learn.microsoft.com/visualstudio/msbuild/msbuild-diagnostic-format-for-tasks Note: There may be further error messages output from runtests scripts, that use this format, which are not explicitly fatal. They may need future fixes. Thanks-to: Dion Williams Ref: https://github.com/curl/curl/discussions/14854#discussioncomment-12382190 Ref: https://github.com/curl/curl/discussions/14854#discussioncomment-12395224 Closes #16583
2025-03-06 04:13:23 +01:00
fprintf(stderr, "Error opening file '%s'\n", libtest_arg2);
return TEST_ERR_MAJOR_BAD; /* if this happens things are major weird */
}
/* get the file size of the local file */
build: add Windows CE / CeGCC support, with CI jobs Make it possible to build curl for Windows CE using the CeGCC toolchain. With both CMake and autotools, including tests and examples, also in CI. The build configuration is the default one with Schannel enabled. No 3rd-party dependencies have been tested. Also revive old code to make Schannel build with Windows CE, including certificate verification. Builds have been throughougly tested. But, I've made no functional tests for this PR. Some parts (esp. file operations, like truncate and seek) are stubbed out and likely broken as a result. Test servers build, but they do not work on Windows CE. This patch substitutes `fstat()` calls with `stat()`, which operate on filenames, not file handles. This may or may not work and/or may not be secure. About CeGCC: I used the latest available macOS binary build v0.59.1 r1397 from 2009, in native `mingw32ce` build mode. CeGCC is in effect MinGW + GCC 4.4.0 + old/classic-mingw Windows headers. It targets Windows CE v3.0 according to its `_WIN32_WCE` value. It means this PR restores portions of old/classic-mingw support. It makes the Windows CE codepath compatible with GCC 4.4.0. It also adds workaround for CMake, which cannot identify and configure this toolchain out of the box. Notes: - CMake doesn't recognize CeGCC/mingw32ce, necessitating tricks as seen with Amiga and MS-DOS. - CMake doesn't set `MINGW` for mingw32ce. Set it and `MINGW32CE` manually as a helper variable, in addition to `WINCE` which CMake sets based on `CMAKE_SYSTEM_NAME`. - CMake fails to create an implib for `libcurl.dll`, due to not recognizing the platform as a Windowsy one. This patch adds the necessary workaround to make it work. - headers shipping with CeGCC miss some things curl needs for Schannel support. Fixed by restoring and renovating code previously deleted old-mingw code. - it's sometime non-trivial to figure out if a fallout is WinCE, mingw32ce, old-mingw, or GCC version-specific. - WinCE is always Unicode. With exceptions: no `wmain`, `GetProcAddress()`. - `_fileno()` is said to convert from `FILE *` to `void *` which is a Win32 file `HANDLE`. (This patch doesn't use this, but with further effort it probably could be.) https://stackoverflow.com/questions/3989545/how-do-i-get-the-file-handle-from-the-fopen-file-structure - WinCE has no signals, current directory, stdio/CRT file handles, no `_get_osfhandle()`, no `errno`, no `errno.h`. Some of this stuff is standard C89, yet missing from this platform. Microsoft expects Windows CE apps to use Win32 file API and `FILE *` exclusively. - revived CeGCC here (not tested for this PR): https://building.enlyze.com/posts/a-new-windows-ce-x86-compiler-in-2024/ On `UNDER_CE` vs. `_WIN32_WCE`: (This patch settled on `UNDER_CE`) - A custom VS2008 WinCE toolchain does not set any of these. The compiler binaries don't contain these strings, and has no compiler option for targeting WinCE, hinting that a vanilla toolchain isn't setting any of them either. - `UNDER_CE` is automatically defined by the CeGCC compiler. https://cegcc.sourceforge.net/docs/details.html - `UNDER_CE` is similar to `_WIN32`, except it's not set automatically by all compilers. It's not supposed to have any value, like a version. (Though e.g. OpenSSL sets it to a version) - `_WIN32_WCE` is the CE counterpart of the non-CE `_WIN32_WINNT` macro. That does return the targeted Windows CE version. - `_WIN32_WCE` is not defined by compilers, and relies on a header setting it to a default, or the build to set it to the desired target version. This is also how `_WIN32_WINNT` works. - `_WIN32_WCE` default is set by `windef.h` in CeGCC. - `_WIN32_WCE` isn't set to a default by MSVC Windows CE headers (the ones I checked at least). - CMake sets `_WIN32_WCE=<ver>`, `UNDER_CE`, `WINCE` for MSVC WinCE. - `_WIN32_WCE` seems more popular in other projects, including CeGCC itself. `zlib` is a notable exception amongst curl dependencies, which uses `UNDER_CE`. - Since `_WIN32_WCE` needs "certain" headers to have it defined, it's undefined depending on headers included beforehand. - `curl/curl.h` re-uses `_WIN32_WCE`'s as a self-guard, relying on its not-(necessarily)-defined-by-default property: https://github.com/curl/curl/blob/25b445e4796bcbf9f842de686a8c384b30f6c2a2/include/curl/curl.h#L77 Toolchain downloads: - Windows: https://downloads.sourceforge.net/cegcc/cegcc/0.59.1/cegcc_mingw32ce_cygwin1.7_r1399.tar.bz2 - macOS Intel: https://downloads.sourceforge.net/cegcc/cegcc/0.59.1/cegcc_mingw32ce_snowleopard_r1397.tar.bz2 Closes #15975
2025-01-10 11:04:02 +01:00
#ifdef UNDER_CE
hd = stat(libtest_arg2, &file_info);
#else
hd = fstat(fileno(hd_src), &file_info);
build: add Windows CE / CeGCC support, with CI jobs Make it possible to build curl for Windows CE using the CeGCC toolchain. With both CMake and autotools, including tests and examples, also in CI. The build configuration is the default one with Schannel enabled. No 3rd-party dependencies have been tested. Also revive old code to make Schannel build with Windows CE, including certificate verification. Builds have been throughougly tested. But, I've made no functional tests for this PR. Some parts (esp. file operations, like truncate and seek) are stubbed out and likely broken as a result. Test servers build, but they do not work on Windows CE. This patch substitutes `fstat()` calls with `stat()`, which operate on filenames, not file handles. This may or may not work and/or may not be secure. About CeGCC: I used the latest available macOS binary build v0.59.1 r1397 from 2009, in native `mingw32ce` build mode. CeGCC is in effect MinGW + GCC 4.4.0 + old/classic-mingw Windows headers. It targets Windows CE v3.0 according to its `_WIN32_WCE` value. It means this PR restores portions of old/classic-mingw support. It makes the Windows CE codepath compatible with GCC 4.4.0. It also adds workaround for CMake, which cannot identify and configure this toolchain out of the box. Notes: - CMake doesn't recognize CeGCC/mingw32ce, necessitating tricks as seen with Amiga and MS-DOS. - CMake doesn't set `MINGW` for mingw32ce. Set it and `MINGW32CE` manually as a helper variable, in addition to `WINCE` which CMake sets based on `CMAKE_SYSTEM_NAME`. - CMake fails to create an implib for `libcurl.dll`, due to not recognizing the platform as a Windowsy one. This patch adds the necessary workaround to make it work. - headers shipping with CeGCC miss some things curl needs for Schannel support. Fixed by restoring and renovating code previously deleted old-mingw code. - it's sometime non-trivial to figure out if a fallout is WinCE, mingw32ce, old-mingw, or GCC version-specific. - WinCE is always Unicode. With exceptions: no `wmain`, `GetProcAddress()`. - `_fileno()` is said to convert from `FILE *` to `void *` which is a Win32 file `HANDLE`. (This patch doesn't use this, but with further effort it probably could be.) https://stackoverflow.com/questions/3989545/how-do-i-get-the-file-handle-from-the-fopen-file-structure - WinCE has no signals, current directory, stdio/CRT file handles, no `_get_osfhandle()`, no `errno`, no `errno.h`. Some of this stuff is standard C89, yet missing from this platform. Microsoft expects Windows CE apps to use Win32 file API and `FILE *` exclusively. - revived CeGCC here (not tested for this PR): https://building.enlyze.com/posts/a-new-windows-ce-x86-compiler-in-2024/ On `UNDER_CE` vs. `_WIN32_WCE`: (This patch settled on `UNDER_CE`) - A custom VS2008 WinCE toolchain does not set any of these. The compiler binaries don't contain these strings, and has no compiler option for targeting WinCE, hinting that a vanilla toolchain isn't setting any of them either. - `UNDER_CE` is automatically defined by the CeGCC compiler. https://cegcc.sourceforge.net/docs/details.html - `UNDER_CE` is similar to `_WIN32`, except it's not set automatically by all compilers. It's not supposed to have any value, like a version. (Though e.g. OpenSSL sets it to a version) - `_WIN32_WCE` is the CE counterpart of the non-CE `_WIN32_WINNT` macro. That does return the targeted Windows CE version. - `_WIN32_WCE` is not defined by compilers, and relies on a header setting it to a default, or the build to set it to the desired target version. This is also how `_WIN32_WINNT` works. - `_WIN32_WCE` default is set by `windef.h` in CeGCC. - `_WIN32_WCE` isn't set to a default by MSVC Windows CE headers (the ones I checked at least). - CMake sets `_WIN32_WCE=<ver>`, `UNDER_CE`, `WINCE` for MSVC WinCE. - `_WIN32_WCE` seems more popular in other projects, including CeGCC itself. `zlib` is a notable exception amongst curl dependencies, which uses `UNDER_CE`. - Since `_WIN32_WCE` needs "certain" headers to have it defined, it's undefined depending on headers included beforehand. - `curl/curl.h` re-uses `_WIN32_WCE`'s as a self-guard, relying on its not-(necessarily)-defined-by-default property: https://github.com/curl/curl/blob/25b445e4796bcbf9f842de686a8c384b30f6c2a2/include/curl/curl.h#L77 Toolchain downloads: - Windows: https://downloads.sourceforge.net/cegcc/cegcc/0.59.1/cegcc_mingw32ce_cygwin1.7_r1399.tar.bz2 - macOS Intel: https://downloads.sourceforge.net/cegcc/cegcc/0.59.1/cegcc_mingw32ce_snowleopard_r1397.tar.bz2 Closes #15975
2025-01-10 11:04:02 +01:00
#endif
if(hd == -1) {
/* can't open file, bail out */
tests: reformat error messages to avoid tripping MSBuild Change the format of error messages sent to stderr from tests and test servers. As a workaround to avoid triggering Visual Studio's MSBuild tool's built-in regexp matcher, and making it mark builds failed for reasons we don't want them to hard fail. Roughly, the pattern to avoid is the word "error" (case-insensitive) in the same line with a colon `:`. It affected GHA/windows MSVC CI jobs, causing flakiness: ``` CUSTOMBUILD : fopen() failed with error : 13 Permission denied [D:\a\curl\curl\bld\tests\test-ci.vcxproj] Error opening file: log/4/smtp_sockfilt.log [...] CUSTOMBUILD : fopen() failed with error : 13 Permission denied [D:\a\curl\curl\bld\tests\test-ci.vcxproj] Error opening file: log/8/imap_sockfilt.log Msg not logged: 00:18:10.656000 > 178 bytes data, server => client [...] TESTDONE: 1629 tests out of 1634 reported OK: 99% Building Custom Rule D:/a/curl/curl/tests/CMakeLists.txt C:\Program Files\Microsoft Visual Studio\2022\Enterprise\MSBuild\Microsoft\VC\v170\Microsoft.CppCommon.targets(254,5): error MSB8066: Custom build for 'D:\a\curl\curl\bld\CMakeFiles\621f80ddbb0fa48179f056ca77842ff0\test-ci.rule;D:\a\curl\curl\tests\CMakeLists.txt' exited with code -1. [D:\a\curl\curl\bld\tests\test-ci.vcxproj] Error: Process completed with exit code 1. ``` Ref: https://github.com/curl/curl/actions/runs/13643149623/job/38137076210?pr=16490#step:14:3125 Ref: https://github.com/curl/curl/actions/runs/13688765792/job/38277961720?pr=16582#step:14:1717 The `IgnoreStandardErrorWarningFormat="true"` MSBuild Exec option controls this behavior: https://learn.microsoft.com/visualstudio/msbuild/exec-task#parameters I couldn't figure out a way to apply it to CMake builds. MSBuid pattern matching rules: https://github.com/dotnet/msbuild/blob/353c0f3d37957cc98bfa6a76b568d70d12193fc3/src/Shared/CanonicalError.cs https://learn.microsoft.com/visualstudio/msbuild/msbuild-diagnostic-format-for-tasks Note: There may be further error messages output from runtests scripts, that use this format, which are not explicitly fatal. They may need future fixes. Thanks-to: Dion Williams Ref: https://github.com/curl/curl/discussions/14854#discussioncomment-12382190 Ref: https://github.com/curl/curl/discussions/14854#discussioncomment-12395224 Closes #16583
2025-03-06 04:13:23 +01:00
fprintf(stderr, "fstat() failed with error (%d) %s\n",
errno, strerror(errno));
tests: reformat error messages to avoid tripping MSBuild Change the format of error messages sent to stderr from tests and test servers. As a workaround to avoid triggering Visual Studio's MSBuild tool's built-in regexp matcher, and making it mark builds failed for reasons we don't want them to hard fail. Roughly, the pattern to avoid is the word "error" (case-insensitive) in the same line with a colon `:`. It affected GHA/windows MSVC CI jobs, causing flakiness: ``` CUSTOMBUILD : fopen() failed with error : 13 Permission denied [D:\a\curl\curl\bld\tests\test-ci.vcxproj] Error opening file: log/4/smtp_sockfilt.log [...] CUSTOMBUILD : fopen() failed with error : 13 Permission denied [D:\a\curl\curl\bld\tests\test-ci.vcxproj] Error opening file: log/8/imap_sockfilt.log Msg not logged: 00:18:10.656000 > 178 bytes data, server => client [...] TESTDONE: 1629 tests out of 1634 reported OK: 99% Building Custom Rule D:/a/curl/curl/tests/CMakeLists.txt C:\Program Files\Microsoft Visual Studio\2022\Enterprise\MSBuild\Microsoft\VC\v170\Microsoft.CppCommon.targets(254,5): error MSB8066: Custom build for 'D:\a\curl\curl\bld\CMakeFiles\621f80ddbb0fa48179f056ca77842ff0\test-ci.rule;D:\a\curl\curl\tests\CMakeLists.txt' exited with code -1. [D:\a\curl\curl\bld\tests\test-ci.vcxproj] Error: Process completed with exit code 1. ``` Ref: https://github.com/curl/curl/actions/runs/13643149623/job/38137076210?pr=16490#step:14:3125 Ref: https://github.com/curl/curl/actions/runs/13688765792/job/38277961720?pr=16582#step:14:1717 The `IgnoreStandardErrorWarningFormat="true"` MSBuild Exec option controls this behavior: https://learn.microsoft.com/visualstudio/msbuild/exec-task#parameters I couldn't figure out a way to apply it to CMake builds. MSBuid pattern matching rules: https://github.com/dotnet/msbuild/blob/353c0f3d37957cc98bfa6a76b568d70d12193fc3/src/Shared/CanonicalError.cs https://learn.microsoft.com/visualstudio/msbuild/msbuild-diagnostic-format-for-tasks Note: There may be further error messages output from runtests scripts, that use this format, which are not explicitly fatal. They may need future fixes. Thanks-to: Dion Williams Ref: https://github.com/curl/curl/discussions/14854#discussioncomment-12382190 Ref: https://github.com/curl/curl/discussions/14854#discussioncomment-12395224 Closes #16583
2025-03-06 04:13:23 +01:00
fprintf(stderr, "Error opening file '%s'\n", libtest_arg2);
fclose(hd_src);
return TEST_ERR_MAJOR_BAD;
}
if(!file_info.st_size) {
tests: reformat error messages to avoid tripping MSBuild Change the format of error messages sent to stderr from tests and test servers. As a workaround to avoid triggering Visual Studio's MSBuild tool's built-in regexp matcher, and making it mark builds failed for reasons we don't want them to hard fail. Roughly, the pattern to avoid is the word "error" (case-insensitive) in the same line with a colon `:`. It affected GHA/windows MSVC CI jobs, causing flakiness: ``` CUSTOMBUILD : fopen() failed with error : 13 Permission denied [D:\a\curl\curl\bld\tests\test-ci.vcxproj] Error opening file: log/4/smtp_sockfilt.log [...] CUSTOMBUILD : fopen() failed with error : 13 Permission denied [D:\a\curl\curl\bld\tests\test-ci.vcxproj] Error opening file: log/8/imap_sockfilt.log Msg not logged: 00:18:10.656000 > 178 bytes data, server => client [...] TESTDONE: 1629 tests out of 1634 reported OK: 99% Building Custom Rule D:/a/curl/curl/tests/CMakeLists.txt C:\Program Files\Microsoft Visual Studio\2022\Enterprise\MSBuild\Microsoft\VC\v170\Microsoft.CppCommon.targets(254,5): error MSB8066: Custom build for 'D:\a\curl\curl\bld\CMakeFiles\621f80ddbb0fa48179f056ca77842ff0\test-ci.rule;D:\a\curl\curl\tests\CMakeLists.txt' exited with code -1. [D:\a\curl\curl\bld\tests\test-ci.vcxproj] Error: Process completed with exit code 1. ``` Ref: https://github.com/curl/curl/actions/runs/13643149623/job/38137076210?pr=16490#step:14:3125 Ref: https://github.com/curl/curl/actions/runs/13688765792/job/38277961720?pr=16582#step:14:1717 The `IgnoreStandardErrorWarningFormat="true"` MSBuild Exec option controls this behavior: https://learn.microsoft.com/visualstudio/msbuild/exec-task#parameters I couldn't figure out a way to apply it to CMake builds. MSBuid pattern matching rules: https://github.com/dotnet/msbuild/blob/353c0f3d37957cc98bfa6a76b568d70d12193fc3/src/Shared/CanonicalError.cs https://learn.microsoft.com/visualstudio/msbuild/msbuild-diagnostic-format-for-tasks Note: There may be further error messages output from runtests scripts, that use this format, which are not explicitly fatal. They may need future fixes. Thanks-to: Dion Williams Ref: https://github.com/curl/curl/discussions/14854#discussioncomment-12382190 Ref: https://github.com/curl/curl/discussions/14854#discussioncomment-12395224 Closes #16583
2025-03-06 04:13:23 +01:00
fprintf(stderr, "File %s has zero size!\n", libtest_arg2);
fclose(hd_src);
return TEST_ERR_MAJOR_BAD;
}
if(curl_global_init(CURL_GLOBAL_ALL) != CURLE_OK) {
fprintf(stderr, "curl_global_init() failed\n");
fclose(hd_src);
return TEST_ERR_MAJOR_BAD;
}
/* get a curl handle */
curl = curl_easy_init();
if(!curl) {
fprintf(stderr, "curl_easy_init() failed\n");
curl_global_cleanup();
fclose(hd_src);
return TEST_ERR_MAJOR_BAD;
}
/* enable uploading */
test_setopt(curl, CURLOPT_UPLOAD, 1L);
/* enable verbose */
test_setopt(curl, CURLOPT_VERBOSE, 1L);
/* specify target */
test_setopt(curl, CURLOPT_URL, URL);
/* now specify which file to upload */
test_setopt(curl, CURLOPT_READDATA, hd_src);
/* Now run off and do what you've been told! */
res = curl_easy_perform(curl);
if(res)
goto test_cleanup;
/* and now upload the exact same again, but without rewinding so it already
is at end of file */
res = curl_easy_perform(curl);
test_cleanup:
/* close the local file */
fclose(hd_src);
curl_easy_cleanup(curl);
curl_global_cleanup();
return res;
}