| Commit message (Collapse) | Author | Age | Files | Lines |
... | |
| | |
|
| | |
|
| |
| |
| |
| | |
(thanks Zash)
|
| |
| |
| |
| | |
setup to avoid a traceback (#262) (thanks Maranda)
|
| | |
|
|/
|
|
| |
IPv6
|
| |
|
| |
|
| |
|
|
|
|
| |
doesn't have an onconnect handler
|
|
|
|
| |
with nil data, so call even when the socket closed cleanly
|
|
|
|
| |
listener.onconnect is missing. onincoming's arguments shall always be non-nil.
|
| |
|
|\ |
|
| | |
|
|/ |
|
| |
|
| |
|
|
|
|
| |
variable...
|
|
|
|
| |
callbacks (thanks darkrain)
|
|
|
|
| |
onconnect() handler, and add support for HTTPS requests to net.http
|
| |
|
|
|
|
| |
sending the request
|
|
|
|
| |
onconnect being called before handshake completion for straight-SSL
|
|
|
|
| |
shows correctly when a handshake exceeded max. allowed iterations)
|
|
|
|
| |
checked despite it not being possible for them to be other than nil
|
|
|
|
| |
a handler, it doesn't mean anything
|
| |
|
|
|
|
| |
addresses
|
| |
|
| |
|
|\ |
|
| |
| |
| |
| | |
better way
|
|\| |
|
| | |
|
| | |
|
| |
| |
| |
| | |
response if a request handler fails to make a response to the client
|
| | |
|
| | |
|
| |
| |
| |
| | |
response if a request handler fails to make a response to the client
|
| | |
|
|/ |
|
| |
|
| |
|
|
|
|
| |
for wantread and wantwrite
|
| |
|
| |
|
| |
|
| |
|
| |
|