blocks|key|95203|text|当管道程序(例如grep)在前一个程序完成对整个页面的写入之前关闭读取管道时，就会发生这种情况。|type|unstyled|depth|inlineStyleRanges|entityRanges|data|95204|在curl+"url"+%7C+grep+-qs+foo中，一旦grep得到了它想要的东西，它就会关闭从curl读取的流。cURL没有预料到这一点，并发出“写入正文失败”错误。|offset|length|style|CODE|95205|一种解决方法是通过一个中间程序来传输流，该中间程序总是在将整个页面提供给下一个程序之前读取整个页面。|95206|例如。|95207|curl+"url"+%7C+tac+%7C+tac+%7C+grep+-qs+foo|code-block|syntax|javascript|95208|tac是一个简单的Unix程序，它读取整个输入页面并颠倒行序(因此我们运行它两次)。因为它必须读取整个输入才能找到最后一行，所以在cURL完成之前，它不会向grep输出任何内容。Grep仍然会关闭读取流，但它只会影响tac，tac不会发出错误。|95209|entityMap^0|0|1|P|0|0|0|0|0|3|0^^$0|@$1|2|3|4|5|6|7|U|8|@]|9|@]|A|$]]|$1|B|3|C|5|6|7|V|8|@$D|W|E|X|F|G]]|9|@]|A|$]]|$1|H|3|I|5|6|7|Y|8|@]|9|@]|A|$]]|$1|J|3|K|5|6|7|Z|8|@]|9|@]|A|$]]|$1|L|3|M|5|N|7|10|8|@]|9|@]|A|$O|P]]|$1|Q|3|R|5|6|7|11|8|@$D|12|E|13|F|G]]|9|@]|A|$]]|$1|S|3|-4|5|6|7|14|8|@]|9|@]|A|$]]]|T|$]]

This happens when a piped program (e.g. grep) closes the read pipe before the previous program is finished writing the whole page.

In <code>curl "url" | grep -qs foo</code>, as soon as grep has what it wants it will close the read stream from curl. cURL doesn't expect this and emits the "Failed writing body" error.

A workaround is to pipe the stream through an intermediary program that always reads the whole page before feeding it to the next program.

E.g.

<pre><code>curl "url" | tac | tac | grep -qs foo
</code></pre>

<code>tac</code> is a simple Unix program that reads the entire input page and reverses the line order (hence we run it twice). Because it has to read the whole input to find the last line, it will not output anything to grep until cURL is finished. Grep will still close the read stream when it has what it's looking for, but it will only affect tac, which doesn't emit an error.

blocks|key|312191|text|对于完整性和将来的搜索：|type|unstyled|depth|inlineStyleRanges|entityRanges|data|312192|这是cURL如何管理缓冲区的问题，缓冲区使用-N选项禁用输出流。|312193|示例：curl+-s+-N+"URL"+%7C+grep+-q+Welcome|offset|length|style|CODE|312194|entityMap^0|0|0|3|Y|0^^$0|@$1|2|3|4|5|6|7|L|8|@]|9|@]|A|$]]|$1|B|3|C|5|6|7|M|8|@]|9|@]|A|$]]|$1|D|3|E|5|6|7|N|8|@$F|O|G|P|H|I]]|9|@]|A|$]]|$1|J|3|-4|5|6|7|Q|8|@]|9|@]|A|$]]]|K|$]]

For completeness and future searches:

It's a matter of how cURL manages the buffer, the buffer disables the output stream with the -N option.

Example:
<code>curl -s -N "URL" | grep -q Welcome</code>

blocks|key|95279|text|另一种可能是，如果使用-o+(输出文件)选项，则目标目录不存在。|type|unstyled|depth|inlineStyleRanges|offset|length|style|CODE|entityRanges|data|95280|例如：如果您有-o+/tmp/download/abc.txt，并且/tmp/下载不存在。|95281|因此，请确保预先创建/存在任何所需的目录，如有必要，请使用--create-dirs选项和-o|95282|entityMap^0|B|2|0|7|O|0|T|D|1A|1|0^^$0|@$1|2|3|4|5|6|7|L|8|@$9|M|A|N|B|C]]|D|@]|E|$]]|$1|F|3|G|5|6|7|O|8|@$9|P|A|Q|B|C]]|D|@]|E|$]]|$1|H|3|I|5|6|7|R|8|@$9|S|A|T|B|C]|$9|U|A|V|B|C]]|D|@]|E|$]]|$1|J|3|-4|5|6|7|W|8|@]|D|@]|E|$]]]|K|$]]

Another possibility, if using the <code>-o</code> (output file) option - the destination directory does not exist.

eg. if you have <code>-o /tmp/download/abc.txt</code> and /tmp/download does not exist.

Hence, ensure any required directories are created/exist beforehand, use the <code>--create-dirs</code> option as well as -<code>o</code> if necessary

blocks|key|312251|text|在我的例子中，服务器用完了磁盘空间。|type|unstyled|depth|inlineStyleRanges|entityRanges|data|312252|使用df+-k+.检查它|offset|length|style|CODE|312253|当我两次尝试通过管道连接tac时，我注意到磁盘空间不足，这在另一个答案中描述：https://stackoverflow.com/a/28879552/336694。它向我显示了错误消息write+error:+No+space+left+on+device。|312254|entityMap|0|LINK|mutability|MUTABLE|url|https://stackoverflow.com/a/28879552/336694^0|0|2|7|0|C|3|2L|10|13|17|0|0^^$0|@$1|2|3|4|5|6|7|R|8|@]|9|@]|A|$]]|$1|B|3|C|5|6|7|S|8|@$D|T|E|U|F|G]]|9|@]|A|$]]|$1|H|3|I|5|6|7|V|8|@$D|W|E|X|F|G]|$D|Y|E|Z|F|G]]|9|@$D|10|E|11|1|12]]|A|$]]|$1|J|3|-4|5|6|7|13|8|@]|9|@]|A|$]]]|K|$L|$5|M|N|O|A|$P|Q]]]]

The server ran out of disk space, in my case.

Check for it with <code>df -k .</code>

I was alerted to the lack of disk space when I tried piping through <code>tac</code> twice, as described in one of the other answers: <a href="https://stackoverflow.com/a/28879552/336694">https://stackoverflow.com/a/28879552/336694</a>. It showed me the error message <code>write error: No space left on device</code>.

blocks|key|312132|text|您可以这样做，而不是使用-o选项：|type|unstyled|depth|inlineStyleRanges|offset|length|style|CODE|entityRanges|data|312133|curl+[url]+>+[file]|312134|entityMap^0|C|2|0|0|J|0^^$0|@$1|2|3|4|5|6|7|J|8|@$9|K|A|L|B|C]]|D|@]|E|$]]|$1|F|3|G|5|6|7|M|8|@$9|N|A|O|B|C]]|D|@]|E|$]]|$1|H|3|-4|5|6|7|P|8|@]|D|@]|E|$]]]|I|$]]

You can do this instead of using <code>-o</code> option:

<code>curl [url] &gt; [file]</code>

blocks|key|95150|text|所以这是一个编码的问题。Iconv解决了这个问题|type|unstyled|depth|inlineStyleRanges|entityRanges|data|95151|curl+'http://www.multitran.ru/c/m.exe?CL=1&s=hello&l1=1'+%7C+iconv+-f+windows-1251+%7C+tr+-dc+'[:print:]'+%7C+...|code-block|syntax|javascript|95152|entityMap^0|0|0^^$0|@$1|2|3|4|5|6|7|I|8|@]|9|@]|A|$]]|$1|B|3|C|5|D|7|J|8|@]|9|@]|A|$E|F]]|$1|G|3|-4|5|6|7|K|8|@]|9|@]|A|$]]]|H|$]]

So it was a problem of encoding. Iconv solves the problem

<pre><code>curl 'http://www.multitran.ru/c/m.exe?CL=1&amp;s=hello&amp;l1=1' | iconv -f windows-1251 | tr -dc '[:print:]' | ...
</code></pre>

blocks|key|312271|text|对我来说，这是一个许可问题。Docker+run是使用用户配置文件调用的，但root是容器内的用户。解决方案是将curl写到/tmp，因为curl对所有用户都有写权限，而不仅仅是根用户。|type|unstyled|depth|inlineStyleRanges|entityRanges|data|312272|我使用了-o选项。|312273|-o+/tmp/文件下载|312274|entityMap^0|0|0|0^^$0|@$1|2|3|4|5|6|7|H|8|@]|9|@]|A|$]]|$1|B|3|C|5|6|7|I|8|@]|9|@]|A|$]]|$1|D|3|E|5|6|7|J|8|@]|9|@]|A|$]]|$1|F|3|-4|5|6|7|K|8|@]|9|@]|A|$]]]|G|$]]

For me, it was permission issue. Docker run is called with a user profile but root is the user inside the container. The solution was to make curl write to /tmp since that has write permission for all users , not just root.

I used the -o option.

-o /tmp/file_to_download

blocks|key|312306|text|如果您正在尝试类似于source+<(+curl+-sS+$url+)的操作，并得到(23)+Failed+writing+body错误，这是因为在bash+3.2+(macOS的默认设置)中不能执行流程替换。|type|unstyled|depth|inlineStyleRanges|offset|length|style|CODE|entityRanges|data|312307|相反，您可以使用此解决方法。|312308|source+/dev/stdin+<<<"$(+curl+-sS+$url+)"|code-block|syntax|javascript|312309|entityMap^0|A|P|16|O|22|8|0|0|0^^$0|@$1|2|3|4|5|6|7|O|8|@$9|P|A|Q|B|C]|$9|R|A|S|B|C]|$9|T|A|U|B|C]]|D|@]|E|$]]|$1|F|3|G|5|6|7|V|8|@]|D|@]|E|$]]|$1|H|3|I|5|J|7|W|8|@]|D|@]|E|$K|L]]|$1|M|3|-4|5|6|7|X|8|@]|D|@]|E|$]]]|N|$]]

If you are trying something similar like <code>source &lt;( curl -sS $url )</code> and getting the <code>(23) Failed writing body</code> error, it is because sourcing a process substitution doesn't work in <code>bash 3.2</code> (the default for macOS).

Instead, you can use this workaround.

<pre><code>source /dev/stdin &lt;&lt;&lt;"$( curl -sS $url )"
</code></pre>

blocks|key|312342|text|在我的例子中，我是这样做的：curl+<blabla>+%7C+jq+%7C+grep+<blibli>|type|unstyled|depth|inlineStyleRanges|offset|length|style|CODE|entityRanges|data|312343|在jq+.上，它起作用了：curl+<blabla>+%7C+jq+.+%7C+grep+<blibli>|312344|entityMap^0|E|Y|0|1|4|D|10|0^^$0|@$1|2|3|4|5|6|7|J|8|@$9|K|A|L|B|C]]|D|@]|E|$]]|$1|F|3|G|5|6|7|M|8|@$9|N|A|O|B|C]|$9|P|A|Q|B|C]]|D|@]|E|$]]|$1|H|3|-4|5|6|7|R|8|@]|D|@]|E|$]]]|I|$]]

In my case, I was doing:
<code>curl &lt;blabla&gt; | jq | grep &lt;blibli&gt;</code>
With <code>jq .</code> it worked: <code>curl &lt;blabla&gt; | jq . | grep &lt;blibli&gt;</code>

blocks|key|95503|text|用sudo尝试这个命令对我来说很有效。例如：|type|unstyled|depth|inlineStyleRanges|offset|length|style|CODE|entityRanges|data|95504|sudo+curl+-O+-k+'https+url+here'|code-block|syntax|javascript|95505|注意:+https+url的-O+(这是大写o，不是零)&+-k。|95506|entityMap^0|1|4|0|0|0^^$0|@$1|2|3|4|5|6|7|O|8|@$9|P|A|Q|B|C]]|D|@]|E|$]]|$1|F|3|G|5|H|7|R|8|@]|D|@]|E|$I|J]]|$1|K|3|L|5|6|7|S|8|@]|D|@]|E|$]]|$1|M|3|-4|5|6|7|T|8|@]|D|@]|E|$]]]|N|$]]

Trying the command with <code>sudo</code> worked for me. For example:
<pre><code>sudo curl -O -k 'https url here'
</code></pre>
note: -O (this is capital o, not zero) &amp; -k for https url.

blocks|key|95481|text|我在做的时候遇到了同样的问题：|type|unstyled|depth|inlineStyleRanges|entityRanges|data|95482|curl+-L+https://packagecloud.io/golang-migrate/migrate/gpgkey+%7C+apt-key+add+-|offset|length|style|CODE|95483|以上查询需要使用root权限执行。|95484|我用下面的方式解决了这个问题：|95485|curl+-L+https://packagecloud.io/golang-migrate/migrate/gpgkey+%7C+sudo+apt-key+add+-|95486|如果在curl之前编写sudo，您将得到Failed+writing+body错误。|95487|entityMap^0|0|0|25|0|0|0|0|2A|0|3|4|B|4|K|J|0^^$0|@$1|2|3|4|5|6|7|R|8|@]|9|@]|A|$]]|$1|B|3|C|5|6|7|S|8|@$D|T|E|U|F|G]]|9|@]|A|$]]|$1|H|3|I|5|6|7|V|8|@]|9|@]|A|$]]|$1|J|3|K|5|6|7|W|8|@]|9|@]|A|$]]|$1|L|3|M|5|6|7|X|8|@$D|Y|E|Z|F|G]]|9|@]|A|$]]|$1|N|3|O|5|6|7|10|8|@$D|11|E|12|F|G]|$D|13|E|14|F|G]|$D|15|E|16|F|G]]|9|@]|A|$]]|$1|P|3|-4|5|6|7|17|8|@]|9|@]|A|$]]]|Q|$]]

I encountered the same problem when doing:
<code>curl -L https://packagecloud.io/golang-migrate/migrate/gpgkey | apt-key add -</code>
The above query needs to be executed using root privileges.
Writing it in following way solved the issue for me:
<code>curl -L https://packagecloud.io/golang-migrate/migrate/gpgkey | sudo apt-key add -</code>
If you write <code>sudo</code> before <code>curl</code>, you will get the <code>Failed writing body</code> error.

It works ok as a single tool:

<pre><code>curl "someURL"
curl -o - "someURL"
</code></pre>

but it doesn't work in a pipeline:

<pre><code>curl "someURL" | tr -d '\n'
curl -o - "someURL" | tr -d '\n'
</code></pre>

it returns:

<pre><code>(23) Failed writing body
</code></pre>

What is the problem with piping the cURL output? How to buffer the whole cURL output and then handle it?

Why does cURL return error "(23) Failed writing body"?

翻译质量差，导致语言生硬或混乱。

没有提供实际的解决方法或示例。

解答不清晰，无法理解或解决问题。

页面排版不美观，阅读体验差。

文章

问答

视频

学习中心

腾讯云实验室

直播

竞赛

腾讯云架构师技术同盟交流圈

腾讯云数据库专区

腾讯云顾问专区

腾讯云原生专区

腾讯混元专区

腾讯云TCE专区

腾讯云Lighthouse专区

腾讯云HAI专区

腾讯云Edgeone专区

腾讯云存储专区

腾讯云智能专区

腾讯轻联专区 

腾讯云开发专区

TAPD专区

腾讯轻量云游戏服专区

腾讯云最具价值专家

腾讯云架构师技术同盟

腾讯云创作之星

腾讯云开发者先锋 

腾讯云代码助手

CODING DevOps

Cloud Studio

SDK中心

API中心

命令行工具

它作为一个工具工作得很好：curl "someURL"curl -o - "someURL"但它不能在管道中工作：curl "someURL" | tr -d '\n'curl -o - "someURL" | tr -d '\n'它返回：(23) Failed writing body通过管道传输cURL输出有什么问题？如何缓冲整个cURL输出，然后进行处理？

问为什么cURL会返回错误"(23)写入body失败“？
EN

回答 11

Stack Overflow用户

Stack Overflow用户

Stack Overflow用户

社区

活动

圈层

关于

腾讯云开发者

热门产品

热门推荐

更多推荐

问为什么cURL会返回错误"(23)写入body失败“？EN

回答 11

Stack Overflow用户

Stack Overflow用户

Stack Overflow用户

社区

活动

圈层

关于

腾讯云开发者

热门产品

热门推荐

更多推荐

问为什么cURL会返回错误"(23)写入body失败“？
EN