lychee/fixtures/TEST_DETAILED_JSON_OUTPUT_ERROR.md

# Test Detailed JSON Output Error

This file is used to test if the error details are parsed properly in the JSON
format.

[The website](https://expired.badssl.com/) produces an SSL expired certificate
error. Such a network error has no status code, but it can be identified by
error status details.
Fix: Bring back error output for links (#1553) With the last lychee release, we simplified the status output for links. While this reduced the visual noise, it also accidentally caused the source of errors to not be printed anymore. This change brings back the additional error information as part of the final report output. Furthermore, it shows the error information in the progress output if verbose mode is activated. Fixes #1487 2024-11-06 23:22:50 +00:00			`# Test Detailed JSON Output Error`
status.rs: Make json output more verbose (#1367) * status.rs: Make json output more verbose Currently if the status response has no status code, json output contains only a text field which gives no real information about the cause of the problem. The patch adds field with more detailed information when the status response contains some details. Signed-off-by: Norbert Kamiński <norbert.kaminski@3mdeb.com> * cli.rs: Test parsing of error details in JSON format Some network error such as SSL has no status code but it can be identified by error status details. This patch adds a test case to verify if the error details are parsed properly in the json format. Signed-off-by: Norbert Kamiński <norbert.kaminski@3mdeb.com> --------- Signed-off-by: Norbert Kamiński <norbert.kaminski@3mdeb.com> 2024-01-30 22:58:18 +00:00
Fix: Bring back error output for links (#1553) With the last lychee release, we simplified the status output for links. While this reduced the visual noise, it also accidentally caused the source of errors to not be printed anymore. This change brings back the additional error information as part of the final report output. Furthermore, it shows the error information in the progress output if verbose mode is activated. Fixes #1487 2024-11-06 23:22:50 +00:00			`This file is used to test if the error details are parsed properly in the JSON`
status.rs: Make json output more verbose (#1367) * status.rs: Make json output more verbose Currently if the status response has no status code, json output contains only a text field which gives no real information about the cause of the problem. The patch adds field with more detailed information when the status response contains some details. Signed-off-by: Norbert Kamiński <norbert.kaminski@3mdeb.com> * cli.rs: Test parsing of error details in JSON format Some network error such as SSL has no status code but it can be identified by error status details. This patch adds a test case to verify if the error details are parsed properly in the json format. Signed-off-by: Norbert Kamiński <norbert.kaminski@3mdeb.com> --------- Signed-off-by: Norbert Kamiński <norbert.kaminski@3mdeb.com> 2024-01-30 22:58:18 +00:00			`format.`

Fix: Bring back error output for links (#1553) With the last lychee release, we simplified the status output for links. While this reduced the visual noise, it also accidentally caused the source of errors to not be printed anymore. This change brings back the additional error information as part of the final report output. Furthermore, it shows the error information in the progress output if verbose mode is activated. Fixes #1487 2024-11-06 23:22:50 +00:00			`[The website](https://expired.badssl.com/) produces an SSL expired certificate`
			`error. Such a network error has no status code, but it can be identified by`
			`error status details.`