Certly log get-roots truncated response

[Rob Stradling]

Hi Ian. My monitor calls get-roots once a day to check for any changes.

https://log.certly.io/ct/v1/get-roots was returning a response of
272,626 bytes, but today it's only returning 65,034 bytes.

It's clearly truncated (rather than deliberate) because there are no "]"
and "}" characters at the end of the response to complete the JSON object.

Is the close proximity of 65,034 to 64K just a coincidence?

--
Rob Stradling
Senior Research & Development Scientist
COMODO - Creating Trust Online

[Ian Carroll]

Uh oh. I'll look into this now. I think it's related to us caching responses.

[Ian Carroll]

It looks like we got bitten by nginx's proxy buffering, which was not adequately set high enough to allow the entire response to buffer. It's been resolved now.

[Pierre Phaneuf]

Responses from the CT server can be potentially fairly large, BTW. A
good example is get-entries, which can return a lot of entries,
depending on the parameters (and the flags to ct-server, since it has
a limit).

> --
> You received this message because you are subscribed to the Google Groups
> "certificate-transparency" group.
> To unsubscribe from this group and stop receiving emails from it, send an
> email to certificate-transp...@googlegroups.com.
> For more options, visit https://groups.google.com/d/optout.