Tags: johan-bjareholt/ureq
Tags
stream: Change unwrap to ConnectionFailed error When writing to socket, the resulting write may fail and return errno 101 "Network Unavailable" and crashing the library (or the dependant of the library). Therefore, if we receive an error, it will be converted to a ConncetionFailed error so that it's handled properly
unit: Add support for setting Send-Buffer-Size on TCP Socket Change-Id: I46c284987333be861217d05daddf6d7752325031
Fallback sending body when server don't understand "Expect:100-continue" If a server does not understand the "Expect: 100-continue" header, it will wait for the body indefinitely. To solve this issue, we add a shorter timeout on reading the response status+headers and if that timeout is hit we send the body anyway.
stream: Divide write timeout by 2 When setting the socket's write timeout, it will instead timeout after double the time set. In order to get the correct behavior, the timeout is divided by 2. We have no idea why it behaves this way, but there is a discussion on stack overflow mentioning it: https://stackoverflow.com/questions/26298040/socket-so-rcvtimeo-timeout-is-double-the-set-value-in-c-vc?noredirect=1&lq=1 Note that this is a local patch and should not be merged upstream.
stream: Divide write timeout by 2 When setting the socket's write timeout, it will instead timeout after double the time set. In order to get the correct behavior, the timeout is divided by 2. We have no idea why it behaves this way, but there is a discussion on stack overflow mentioning it: https://stackoverflow.com/questions/26298040/socket-so-rcvtimeo-timeout-is-double-the-set-value-in-c-vc?noredirect=1&lq=1 Note that this is a local patch and should not be merged upstream.
stream: Divide write timeout by 2 When setting the socket's write timeout, it will instead timeout after double the time set. In order to get the correct behavior, the timeout is divided by 2. We have no idea why it behaves this way, but there is a discussion on stack overflow mentioning it: https://stackoverflow.com/questions/26298040/socket-so-rcvtimeo-timeout-is-double-the-set-value-in-c-vc?noredirect=1&lq=1 Note that this is a local patch and should not be merged upstream.
stream: Divide write timeout by 2 When setting the socket's write timeout, it will instead timeout after double the time set. In order to get the correct behavior, the timeout is divided by 2. We have no idea why it behaves this way, but there is a discussion on stack overflow mentioning it: https://stackoverflow.com/questions/26298040/socket-so-rcvtimeo-timeout-is-double-the-set-value-in-c-vc?noredirect=1&lq=1 Note that this is a local patch and should not be merged upstream.
response: Remove error wrapper in read_next_line
The wrapper ended up creating a bug where the resulting Error from
read_next_line() would be a ureq::Error -> std::io::Error ->
-> ureq::Error -> std::io::Error, where "->" refers to the source.
This ended up printing "Network Error: Network Error: {some reason}",
but it was also a weird behavior. Thus, we removed the wrapper between
the std::io::Error's and bundled them together into a single
std::io::Error. This will make read_next_line() return an Error which
looks like this: ureq::Error -> std::io::Error.
response: Remove error wrapper in read_next_line
The wrapper ended up creating a bug where the resulting Error from
read_next_line() would be a ureq::Error -> std::io::Error ->
-> ureq::Error -> std::io::Error, where "->" refers to the source.
This ended up printing "Network Error: Network Error: {some reason}",
but it was also a weird behavior. Thus, we removed the wrapper between
the std::io::Error's and bundled them together into a single
std::io::Error. This will make read_next_line() return an Error which
looks like this: ureq::Error -> std::io::Error.
PreviousNext