Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Option --debug-headers doesn't always work #514

Closed
robertbruntz opened this issue Jul 10, 2024 · 0 comments
Closed

Option --debug-headers doesn't always work #514

robertbruntz opened this issue Jul 10, 2024 · 0 comments
Assignees
Labels

Comments

@robertbruntz
Copy link

Describe the bug

Running check_ssl_cert from Bash with the "--debug-headers" flag ("Store the retrieved HTLM headers in the headers.txt file") does not always produce the expected headers.txt file. E.g., "./check_ssl_cert --debug-headers -H github.com" does not produce the file, whereas "./check_ssl_cert --debug-headers --all-local -H github.com" does produce the file. I have not tested many other flags to see which ones do and do not cause file production. "--all-local" does; "-v" does not.

To Reproduce

  1. Clone the repo
  2. Run "./check_ssl_cert --debug-headers -H github.com"; should not produce headers.txt
  3. Run "./check_ssl_cert --debug-headers --all-local -H github.com"; should produce headers.txt (with the HTTP response headers from github.com)

Expected behavior

Running check_ssl_cert with the --debug-headers flag should always produce headers.txt

System (please complete the following information):

  • OS: Linux
  • OS version: 3.10.0-1160.108.1.el7.x86_64
  • check_ssl_cert version: 2.81.1
  • OpenSSL version (openssl version): 1.0.2k-fips

Additional context/output

(none)

@matteocorti matteocorti self-assigned this Jul 10, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

No branches or pull requests

2 participants