Proxy server squid, ssl_bump explain what is the difference between peek and stare?

Question

Squid

There is a proxy configured to monitor visited https sites without replacing the certificate, everything works, but sometimes such an error appears in the browser

after going to the address bar and pressing Enter, the site opens successfully, there are no errors in the logs, it rarely appears and it is not possible to repeat the error on purpose. In the process of searching for a solution and reading the documentation , I got into a dead end, I can’t understand the difference between ssl_bump peek step1and ssl_bump stare step1, what is the difference? The documentation says:
peek

When a peek rule matches during step1, Squid proceeds to step2 where it parses the TLS Client Hello and extracts SNI (if any). when a peek rule matches during step 2, Squid proceeds to step3 where it parses the TLS Server Hello and extracts server certificate while preserving the possibility of splicing the client and server connections; peeking at the server certificate usually precludes future bumping (see Limitations).

stare

When a stare rule matches during step1, Squid proceeds to step2 where it parses the TLS Client Hello and extracts SNI (if any). when a stare rule matches during step2, Squid proceeds to step3 where it parses the TLS Server Hello and extracts server certificate while preserving the possibility of bumping the client and server connections; staring at the server certificate usually precludes future splicing (see Limitations).

The difference in the description is minimal, but my knowledge of English is not enough to understand what is the difference between them? When to use one, and when to use the other.
Can someone explain in human language what's what?

Answer 1

I collected 4 squids with the same config, the flight is normal, the problem has not been manifested for almost a month...

Answer 2

I could be wrong, this is how I remember it. Squid can work with SSL connections in several modes.
1. peek + splice - in this mode, it simply pulls out the resource name using SNI and the client continues to work with the resource. Those. the certificate is not replaced. This mode is suitable for transparent proxy
2. stare + bump - and here, the squid will also get into the "conversation" between the client and the server, that is, quite a classic MITM.