Closed lpc921 closed 4 years ago
Hi! Thanks for reporting.
We'll investigate that case as soon as we get some time for it.
Hi, @lpc921!
Can you try the current version from 0.6-dev branch? I think we've found and fixed the problem.
Hi, @eao197
Thanks so much for the fast response. I can confirm this issue is fixed for me when sending a file to the client.
I still need to catch and ignore SIGPIPE. I guess that's the correct / safe way to handle sendfile with partially-read response?
I still need to catch and ignore SIGPIPE. I guess that's the correct / safe way to handle sendfile with partially-read response?
I don't know how sendfile
and sendfile64
OS-calls are implemented under the hood. So it seems that on Linux (and other flavors of Unixes) the behavior of sendfile
looks like the behavior of write
for a pipe so you have to deal with SIGPIPE.
The fix for that issue is in v.0.6.4 released today. This version is available via Conan.
I am not sure the way I am using the library is correct. I have a following scenario that causes segfault on the server. Could you tell me how to prevent it from happening? I am using Ubuntu 18.04 gcc 8.3.0 restinio 0.6.3
Here is the debugger output:
Console logger. The long request starts at [2020-02-07 11:04:14.673]