Update rippled-example.cfg to clarify usage of ssl_cert and ssl_chain

[ggprod]

High Level Overview of Change

update notes for ssl_cert and ssl_chain to clarify that ssl_chain must be used when the certificate includes one or more intermediates

Context of Change

Type of Change

• Bug fix (non-breaking change which fixes an issue)
• New feature (non-breaking change which adds functionality)
• Breaking change (fix or feature that would cause existing functionality to not work as expected)
• Refactor (non-breaking change that only restructures code)
• Tests (You added tests for code that already exists, or your new feature included in this PR)
• Documentation Updates
• Release

[ggprod]

@intelliot should I add another comment on ssl_verify (when set to 1 it seems to prevent commands like rippled server_info from working)?

Not sure if other config impacts that or not but found that these commands gave:

{
   "error" : "internal",
   "error_code" : 73,
   "error_message" : "Internal error.",
   "error_what" : "no response from server"
}

even though doing them via curl or externally they worked fine

[ckeshava]

@ggprod I have observed this error when the local rippled server was stopped (Through SIGKILL or the rippled stop command)
When you use curl, you are connecting to a non-local rippled server right?

[ckeshava]

I'm surprised to see these two errors in the CI tests, despite not having any code changes. Do you observe this in your local unit tests too? @ggprod

1> #8 failed: ShardArchiveHandler_test.cpp(420)
1> #9 failed: ShardArchiveHandler_test.cpp(427)

[ggprod]

I'm surprised to see these two errors in the CI tests, despite not having any code changes. Do you observe this in your local unit tests too? @ggprod

1> #8 failed: ShardArchiveHandler_test.cpp(420)
1> #9 failed: ShardArchiveHandler_test.cpp(427)

I didn't run unit tests as I only made changes in that one file (and only among the comments)

[ggprod]

@ggprod I have observed this error when the local rippled server was stopped (Through SIGKILL or the rippled stop command) When you use curl, you are connecting to a non-local rippled server right?

in my case rippled was running fine and was responding to the same request when done using curl (either internally via localhost or externally)

[ggprod]

I am closing this PR and will re-do it as I didn't sign my commit

[intelliot]

Replaced by #4667