Stefan Eissing
Stefan Eissing
### I did this ``` CURL_DBG_SOCK_RMAX=4 ./runtests.pl -v 982 ``` ### I expected the following The test to succeed. The difference is that `pop3_state_starttls_resp()` in `pop3.c:789` behaves differently depending on...
- from `conn->bits.authneg` to `data->req.authneg` - AFAICT, this is a property of the request about to be made and not a property of the connection - in multiuse connections, transfer...
- when data arrived in several chunks, the collection into the passed buffer always started at offset 0, overwriting the data already there.
### Curl_read/Curl_write clarifications - replace `Curl_read()`, `Curl_write()` and `Curl_nwrite()` to clarify when and at what level they operate - send/recv of transfer related data is now done via `Curl_xfer_send()/Curl_xfer_recv()` which...
- set our idle timeout as transport parameter - query negotiated idle timeout for connection alive checks - query number of available bidi streams on a connection - use write_ex2...
Refactoring of the client writer that passes the data to the client/application's callback functions. - split out into own source `cw-out.[ch]` from `sendf.c` - move `tempwrite` and `tempcount` from `data->state`...
- add a client writer that does "push" response headers written to the client if the headers api is enabled - remove special handling in sendf.c - needs to be...
In curl, we added tests with large request headers and observe unexpected behaviour with quiche. Maybe we are holding it wrong. The case is simple, a request with ~64KB headers...
From a mail to apache-users mailing list: ``` I had an interesting dilemma come up. I want to start using mod_md, but needed an answer as to what to do...
- use facilities provided by client readers better - work also for non-uploading requests like GET/HEAD - update documentation