Commit message (Collapse) | Author | Age | Files | Lines | |
---|---|---|---|---|---|
* | net.server_epoll: Use monotonic time for scheduling | Kim Alvefur | 2019-12-08 | 1 | -9/+11 |
| | | | | Timer API of passing wallclock time remains | ||||
* | net.server_epoll: Change timer rescheduling method to match util.timer | Kim Alvefur | 2019-12-08 | 1 | -2/+3 |
| | | | | | Relative to current time instead of absolute time, in preparation for switching to monotonic time. | ||||
* | net.server_epoll: Remove unused function for adding timer at absolute time | Kim Alvefur | 2019-12-08 | 1 | -8/+3 |
| | | | | This won't make sense if we switch to monotonic time | ||||
* | net.server_epoll: Add debug logging for delayed reading | Kim Alvefur | 2019-12-07 | 1 | -0/+1 |
| | | | | | | | | | | | | | | | | In :onreadable, if there is still buffered incoming data after reading from the socket (as indicated by the :dirty method, usually because LuaSocket has an 8k buffer that's full but it read a smaller amount), another attempt to read is scheduled via this :pausefor method. This is also called from some other places where it would be pointless to read because there shouldn't be any data. In the delayed read case, this should report that the socket is "dirty". If it reports that the socket is "clean" then the question is where the buffer contents went? If this doesn't get logged after the scheduled time (0.000001s by default) then this would suggests a problem with timer or scheduling. | ||||
* | net.server_epoll: Save log tag in a field on FD watchers too | Kim Alvefur | 2019-11-17 | 1 | -2/+4 |
| | | | | As with 0e1701197722 | ||||
* | Back out c8aa66595072: Extra changes accidentally included | Kim Alvefur | 2019-11-17 | 1 | -5/+3 |
| | |||||
* | net.server_epoll: Save log tag in a field on FD watchers too | Kim Alvefur | 2019-11-17 | 1 | -3/+5 |
| | | | | As with 0e1701197722 | ||||
* | net.server_epoll: Improve read timeout debug messages | Kim Alvefur | 2019-10-19 | 1 | -2/+2 |
| | |||||
* | net.server_epoll: Clarify a debug message | Kim Alvefur | 2019-10-19 | 1 | -1/+1 |
| | | | | Writing what? The data that's been buffered for writing | ||||
* | net.server_epoll: Save IP and port from connection creation call | Kim Alvefur | 2019-10-12 | 1 | -0/+4 |
| | | | | Might come out of :getpeername different later but at least it's something. | ||||
* | server_epoll: Log full string represestation when connected | Kim Alvefur | 2019-10-12 | 1 | -1/+1 |
| | | | | Since they may have been unknown when the connection was created. | ||||
* | net.server_epoll: Handle getpeer/sockname returning a normal error | Kim Alvefur | 2019-10-12 | 1 | -2/+2 |
| | | | | | These will sometimes return nil, "Transport not connected" but not throw a hard error. This shouldn't be treated as success. | ||||
* | net.server_epoll: Fix to get remote IP on direct TLS connections | Kim Alvefur | 2019-10-12 | 1 | -0/+1 |
| | | | | | | | | A Direct TLS connection (eg HTTPS) gets turned into a LuaSec handle before the :updatenames call done in the :connect method. LuaSec does not expose the :getpeername and :getsockname methods, so the addresses remain obscured, making debugging trickier since the actual IP addrerss connected to does not show up. | ||||
* | net.server_epoll: Move a log message to improve ordering | Kim Alvefur | 2019-10-12 | 1 | -1/+1 |
| | | | | It was weird that it said "Prepared to start TLS" before "Client .. created" | ||||
* | net.server_epoll: Guard against nil return from TLS info method | Kim Alvefur | 2019-10-06 | 1 | -2/+2 |
| | |||||
* | net.server_epoll: Log TLS version and cipher for all completed handshakes | Kim Alvefur | 2019-10-06 | 1 | -1/+6 |
| | | | | | The similar logging in mod_c2s and mod_s2s does not cover all connections, like HTTPS or other Direct TLS ports. | ||||
* | net.server_epoll: Log size of partial writes (debug) | Kim Alvefur | 2019-10-05 | 1 | -0/+1 |
| | |||||
* | net.server_epoll: Return early when attepting to set write lock state to ↵ | Kim Alvefur | 2019-10-05 | 1 | -0/+6 |
| | | | | | | current state Reduces needless duplication of work and log messages.. | ||||
* | net.server_epoll: Correct indentation | Kim Alvefur | 2019-09-29 | 1 | -2/+2 |
| | |||||
* | net.server_epoll: Ignore unused self argument [luacheck] | Kim Alvefur | 2019-09-29 | 1 | -1/+1 |
| | |||||
* | net.server_epoll: Fix link function to not replace listeners | Kim Alvefur | 2019-09-29 | 1 | -9/+5 |
| | | | | | | | | mod_proxy65 calls link twice, once for each direction. This would overwrite the listeners with one that has the previous listeners as metatable.__index, but none of the others. This takes advantage of 94c584d67533 to improve this. | ||||
* | net.server_epoll: Handle read size argument to link | Kim Alvefur | 2019-09-29 | 1 | -1/+2 |
| | |||||
* | net.server_epoll: Add some timeout related logging | Kim Alvefur | 2019-09-29 | 1 | -0/+3 |
| | |||||
* | net.server_epoll: Add debug logging for various connection events | Kim Alvefur | 2019-09-29 | 1 | -0/+6 |
| | |||||
* | net.server_epoll: Make log tag accessible as a field | Kim Alvefur | 2019-09-29 | 1 | -1/+3 |
| | | | | To allow referencing connections by id instead of tostring form | ||||
* | net.server_epoll: Make it easy to override handler for incoming data | Kim Alvefur | 2019-09-29 | 1 | -2/+7 |
| | |||||
* | net.server: Handle server name (SNI) as extra argument | Kim Alvefur | 2019-09-01 | 1 | -0/+6 |
| | | | | | | Code added in 75d2874502c3, 9a905888b96c and adc0672b700e uses this field. See #409 and #1408 | ||||
* | net.server: Accept and save an 'extra' field for client connections | Kim Alvefur | 2019-09-01 | 1 | -5/+6 |
| | | | | | This lets code attach some extra data to be attached to client connections. | ||||
* | net.server_epoll: Add support for opportunistic writes | Kim Alvefur | 2019-08-28 | 1 | -0/+8 |
| | | | | | | | | This tries to flush data to the underlying sockets when receiving writes. This should lead to fewer timer objects being around. On the other hand, this leads to more and smaller writes which may translate to more TCP/IP packets being sent, depending on how the kernel handles this. This trades throughput for lower latency. | ||||
* | server_epoll: Add native support for per socket bandwith limits | Kim Alvefur | 2016-12-18 | 1 | -0/+17 |
| | |||||
* | net.server_epoll: Remove unused local [luacheck] | Kim Alvefur | 2019-07-26 | 1 | -1/+0 |
| | |||||
* | net.server_epoll: Overhaul logging with one log sink per connection | Kim Alvefur | 2019-07-26 | 1 | -23/+41 |
| | |||||
* | net.server_epoll: Deprecate libevent emulation layer | Kim Alvefur | 2019-07-24 | 1 | -0/+1 |
| | |||||
* | net.server_epoll: Return errors from creating sockets | Kim Alvefur | 2019-07-23 | 1 | -0/+1 |
| | | | | | | Prevents error from attempting to index nil conn on such failure. Silences luacheck warning about the 'err' variable being unused | ||||
* | net.server_epoll: Add experimental option to close connections in case of ↵ | Kim Alvefur | 2019-05-25 | 1 | -0/+8 |
| | | | | | | | listener error Sometimes such errors leave sessions in an inconsistent state, so it might be better to close them early. | ||||
* | net.server_epoll: Return listener error message | Kim Alvefur | 2019-05-25 | 1 | -1/+1 |
| | |||||
* | Merge 0.11->trunk | Kim Alvefur | 2019-05-04 | 1 | -1/+1 |
|\ | |||||
| * | net.server_epoll: Restore wantread flag after pause (fixes #1354) | Kim Alvefur | 2019-05-04 | 1 | -1/+1 |
| | | | | | | | | | | | | | | | | | | If a chunk of data has been received that is larger than the amount read at a time, then the connection is paused for a short time after which it tries to read some more. If, after that, there is still more data to read, it should do the same thing. However, because the "want read" flag is removed and was restored after the delayed reading, it would not schedule another delayed read. | ||||
* | | Merge 0.11->trunk | Kim Alvefur | 2019-03-28 | 1 | -6/+9 |
|\| | |||||
| * | net.server_epoll: Skip delayed continuation read on paused connections | Kim Alvefur | 2019-03-28 | 1 | -1/+1 |
| | | | | | | | | | | | | This should prevent #1333 in cases where LuaSockets buffer is "dirty", i.e. contains more data after a read, where it gets resumed with a short delay. | ||||
| * | net.server_epoll: Handle LuaSec wantread/wantwrite conditions before ↵ | Kim Alvefur | 2019-03-28 | 1 | -5/+8 |
| | | | | | | | | | | | | | | callbacks (fixes #1333) This prevents the :set(true) call from resuming a connection that was paused in the onincoming callback. | ||||
* | | net.server_epoll: Optimize timer handling | Kim Alvefur | 2019-03-12 | 1 | -53/+30 |
| | | |||||
* | | net.server: Only add alternate SNI contexts if at least one is provided | Kim Alvefur | 2019-03-11 | 1 | -1/+1 |
| | | | | | | | | Fixes use of <starttls/> when a client sends SNI, which would send no certificate otherwise. | ||||
* | | net.server_epoll: Add support for SNI (#409) | Kim Alvefur | 2019-03-10 | 1 | -0/+8 |
| | | |||||
* | | net.server: New API for creating server listeners | Kim Alvefur | 2018-09-13 | 1 | -4/+14 |
| | | | | | | | | server.listen(interface, port, listeners, options); | ||||
* | | net.server_epoll: Increase send_timeout to 3 minutes (to match server_event) | Kim Alvefur | 2019-02-09 | 1 | -1/+1 |
| | | | | | | | | The separate connect_timeout means we can afford a longer send_timeout | ||||
* | | net.server_epoll: Separate timeout for initial connection attempts | Kim Alvefur | 2019-02-09 | 1 | -1/+4 |
| | | | | | | | | server_event has this separation already | ||||
* | | Merge 0.11->trunk | Kim Alvefur | 2019-02-09 | 1 | -5/+5 |
|\| | |||||
| * | net.server_epoll: Rename handshake_timeout to ssl_handshake_timeout (fixes ↵ | Kim Alvefur | 2019-02-09 | 1 | -3/+3 |
| | | | | | | | | | | | | #1319) This is to match server_event, see 430797a8fc81 | ||||
| * | net.server_epoll: Use send_timeout for write timout like other ↵ | Kim Alvefur | 2019-02-07 | 1 | -2/+2 |
| | | | | | | | | implementations (fixes #1316) |