> For the complete documentation index, see [llms.txt](https://sunzsh.gitbook.io/xiaoshan.bug/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://sunzsh.gitbook.io/xiaoshan.bug/chrome-kai-fa-zhe-zhua-bao-gong-ju-copycurl-de-yi-ge-shi-yong-chang-jing.md).

# chrome开发者抓包工具copy-cURL的一个使用场景

{% embed url="<https://v.douyin.com/r6pGFrH/>" %}

{% embed url="<https://www.bilibili.com/video/BV13a411h7Ki/>" %}

chrome 的开发者工具里抓到的包

可以直接复制成 cURL 的命令

那这个功能我在一个场景下就经常用

比方说这是一个测试环境

然后呢我们就发现

比如说某一个筛选条件

他查询的结果就不太对

然后呢我们想本地调试一下这接口

让他请求一下本地的接口

我们就可以复制成 cURL

然后呢打开终端然后粘贴

然后按 ctrl a （按住回到最上面）

然后 ctrl + 右箭头 来到这，把它改成

本地的 ip

然后呢比如8080，然后回车，这样就行了

当然了 （现在）我本地没有启动任何服务哈


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation by asking a question.

Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:

```
GET https://sunzsh.gitbook.io/xiaoshan.bug/chrome-kai-fa-zhe-zhua-bao-gong-ju-copycurl-de-yi-ge-shi-yong-chang-jing.md?ask=<question>&goal=<user_goal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.