| Commit message (Collapse) | Author | Age | Files | Lines |
... | |
| |
| |
| |
| | |
don't understand the OpenSSL error
|
| | |
|
| | |
|
|\| |
|
| |
| |
| |
| | |
outgoing s2s connection (thanks foucault)
|
| | |
|
| |
| |
| |
| | |
missing.
|
| | |
|
| | |
|
| | |
|
| | |
|
|\ \ |
|
| | |
| | |
| | |
| | | |
key/certificate file
|
| | | |
|
|/ /
| |
| |
| | |
more explicit about what it does
|
| | |
|
| | |
|
| |
| |
| |
| | |
data is received by a destroyed session
|
| | |
|
| | |
|
| |
| |
| |
| | |
for s2s-stream-features event for consistency.
|
| | |
|
| |
| |
| |
| | |
sessions table
|
| | |
|
| | |
|
| |
| |
| |
| | |
(module.environment within plugins).
|
| | |
|
| | |
|
| | |
|
| | |
|
| | |
|
| | |
|
| | |
|
| | |
|
| | |
|
| | |
|
| | |
|
| | |
|
| | |
|
| | |
|
| | |
|
| | |
|
| | |
|
| | |
|
| | |
|
| | |
|
| |
| |
| |
| | |
outgoing s2s connection (thanks foucault)
|
| |
| |
| |
| | |
headers recently? :)
|
| |
| |
| |
| | |
was never reached) - s2s stream errors now reported properly
|
| |
| |
| |
| | |
stream_error_tag so that callers don't need to be so worried about the separator we use
|