I was trying to read up on it and just based off of the manual it seems not to make sense if I’m not using --silent alongside it, but I found this one article stating otherwise: https://nrogap.medium.com/show-error-response-for-curl-64666cd64330

I can’t figure out if it’s just AI slop or badly researched since it doesn’t even show a real URL to test the commands against.

Manual entry:

       -S, --show-error
              When used with  -s,  --silent,  it
              makes  curl  show an error message
              if it fails.

              This option is global and does not
              need  to be specified for each use
              of -:, --next.

              Providing -S, --show-error  multi‐
              ple  times  has  no  extra effect.
              Disable it again  with  --no-show-
              error.

              Example:
               curl --show-error --silent https://
example.com

              See also --no-progress-meter.
  • QuazarOmega@lemy.lolOP
    link
    fedilink
    arrow-up
    1
    ·
    edit-2
    3 hours ago

    I couldn’t find an endpoint to test this with, picking out a random inexistent domain I could just see that without parameters I get the errors, with silent I get none, with show-error I get the same output as no parameters, with both I get the same output as no parameters again.
    This is as far as I can get without reading into the source code, I already searched on the internet with no luck because all others posts I could find assume it is paired with another parameter

    • stupid_asshole69 [none/use name]@hexbear.net
      link
      fedilink
      English
      arrow-up
      1
      ·
      9 minutes ago

      So based on both the man page and your findings, it’s safe to assume that the medium article is wrong.

      We both see different behavior than what it suggests and that behavior is in alignment with a different, trustworthy source of documentation!

      • QuazarOmega@lemy.lolOP
        link
        fedilink
        arrow-up
        1
        ·
        1 hour ago

        I think so too, but I wanted a confirmation. I tried that website as well, but with it I could only get error messages if I also provide --fail to error on HTTP error codes