Commit message (Collapse) | Author | Files | Lines | ||
---|---|---|---|---|---|
2022-03-23 | Update URL references to source repository | Caleb Maclennan | 2 | -5/+5 | |
2022-03-23 | Move doc→docs so we can serve it with GitHub Pages | Caleb Maclennan | 19 | -20/+20 | |
2022-03-22 | fix(docs) references to some constants added (#359) | Thijs Schreijer | 2 | -4/+10 | |
2022-03-22 | fix(docs) fix html linter issues in the docs (#358) | Thijs Schreijer | 11 | -934/+938 | |
2022-03-22 | http.lua: set transfer-encoding if source and no content-length | Julian Squires | 1 | -0/+7 | |
If a source is specified without a content-length header, LuaSocket sends the data in the chunked transfer coding; however, it doesn't set the transfer-encoding header. While I recognize that the user can set this manually, this is a gotcha that has caught me multiple times. RFC7230, section 3.3.3 (https://tools.ietf.org/html/rfc7230#section-3.3.3) is clear about this; if neither content-length nor transfer-encoding chunked are specified, the request message body length is zero. While some servers may ignore this, I have encountered several that follow the RFC in this regard, most recently golang's net/http. | |||||
2022-03-22 | Add src\compat.c to mime.vcxproj and socket.vcxproj | E. Westbrook | 2 | -0/+2 | |
2022-03-21 | src/ltn12.lua: remove duplicated codes | david | 1 | -3/+3 | |
2022-03-19 | chore: Drop rockspec for never-published RC2 release | Caleb Maclennan | 1 | -134/+0 | |