| Commit message (Collapse) | Author | Age | Files | Lines |
|
|
|
|
|
|
| |
It appears that a bad gRPC code is already captured as part of err. In
other words, additional detail can be inside the following error clause.
See example in CTFE's addChainInternal() function.
|
| |
|
| |
|
|
|
|
|
| |
Moved structures for in/out HTTP data into reqres.go and added basic
doc comments. A few minor edits as well to make things consistent.
|
| |
|
|
|
|
|
|
| |
If the provided tree size is (mostly) valid the Trillian back-end is
asked to provide an inclusion proof, which is then placed in an
InclusionProofV1 structure and returned as a JSON object.
|
|
|
|
|
| |
If the provided range is (mostly) valid the corresponding log entries
are fetched from the Trillian back-end and returned as a JSON object.
|
| |
|
|
|
|
|
| |
If the POSTed StItem can be parsed without errors it is handed over to
the Trillian back-end.
|
|
An STFE server instance that dials the Trillian gRPC back-end, and which
listens on six different HTTP endpoints but without any actual processing.
|