[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: [Wget-dev] wget2 | Fix for -p -nc Bug (!416)
From: |
Kumar Mallikarjuna |
Subject: |
Re: [Wget-dev] wget2 | Fix for -p -nc Bug (!416) |
Date: |
Wed, 27 Mar 2019 15:14:57 +0000 |
Kumar Mallikarjuna commented on a discussion on tests/test-p-nc.c:
> + { urls[14].name + 1, urls[14].body }, // import1.css
> + { urls[15].name + 1, urls[15].body }, // import2.css
> + { urls[16].name + 1, urls[16].body }, // background.css
> + { NULL } },
> + 0);
> +
> + // test-p-nc (with existing files)
> + wget_test(
> + WGET_TEST_OPTIONS, "-p -nc -nH",
> + WGET_TEST_REQUEST_URL, "index.html",
> + WGET_TEST_EXPECTED_ERROR_CODE, 0,
> + WGET_TEST_EXISTING_FILES, &(wget_test_file_t []) {
> + { urls[0].name + 1, modified_index_html },
> + { urls[4].name + 1, "modified image" },
> + { NULL } },
> + WGET_TEST_EXPECTED_FILES, &(wget_test_file_t []) {
The test fails for this case. Is the expected behavior suppose to be: keep the
latest modification (done either on client or server) on the client system, or
keep the file as it is on the client system, do not update? This solution is
working in accord with the latter.
--
Reply to this email directly or view it on GitLab:
https://gitlab.com/gnuwget/wget2/merge_requests/416#note_154729849
You're receiving this email because of your account on gitlab.com.
- Re: [Wget-dev] wget2 | Fix for -p -nc Bug (!416), (continued)
- Message not available
- Message not available
Re: [Wget-dev] wget2 | Fix for -p -nc Bug (!416), Kumar Mallikarjuna, 2019/03/22
Message not available
Message not available
Message not available
Re: [Wget-dev] wget2 | Fix for -p -nc Bug (!416), Kumar Mallikarjuna, 2019/03/22
Message not available