blocks|key|34661|text|我终于找到了答案。|type|unstyled|depth|inlineStyleRanges|entityRanges|data|34662|Charles+3.11.2与WebSocket完美配合。|offset|length|style|BOLD|34663|我使用socketIO，所以我已经看到在协商阶段发送http请求，但是我错过了websockets流量。|34664|在一开始，socketIO尝试使用轮询，然后切换到使用websockets。|34665|当您转到状态为“正在发送请求正文”的请求时，可以看到websocket流量，该请求实际上是wss://+request。|34666|你甚至有一个专门的标签来处理这种流量。其余的消息就会出现在那里。|34667|​|34668|📷|atomic|34669|34670|PS1。确保您已正确连接到套接字，然后它将出现在Charles中。|34671|PS2。我建议使用socketIO，对于像websockets这样的全双工通信来说，这是一个很好的增强。|34672|entityMap|0|LINK|mutability|MUTABLE|url|http://socket.io/|1|IMAGE|IMMUTABLE|imageUrl|https://ask.qcloudimg.com/http-save/yehe-900000/f28233d7a507b39021d253607fa8f2ee.png|imageAlt^0|0|0|T|0|Z|H|3|8|0|0|0|0|0|0|0|1|1|0|0|0|0^^$0|@$1|2|3|4|5|6|7|1D|8|@]|9|@]|A|$]]|$1|B|3|C|5|6|7|1E|8|@$D|1F|E|1G|F|G]]|9|@]|A|$]]|$1|H|3|I|5|6|7|1H|8|@$D|1I|E|1J|F|G]]|9|@$D|1K|E|1L|1|1M]]|A|$]]|$1|J|3|K|5|6|7|1N|8|@]|9|@]|A|$]]|$1|L|3|M|5|6|7|1O|8|@]|9|@]|A|$]]|$1|N|3|O|5|6|7|1P|8|@]|9|@]|A|$]]|$1|P|3|Q|5|6|7|1Q|8|@]|9|@]|A|$]]|$1|R|3|S|5|T|7|1R|8|@]|9|@$D|1S|E|1T|1|1U]]|A|$]]|$1|U|3|Q|5|6|7|1V|8|@]|9|@]|A|$]]|$1|V|3|W|5|6|7|1W|8|@]|9|@]|A|$]]|$1|X|3|Y|5|6|7|1X|8|@]|9|@]|A|$]]|$1|Z|3|-4|5|6|7|1Y|8|@]|9|@]|A|$]]]|10|$11|$5|12|13|14|A|$15|16]]|17|$5|18|13|19|A|$1A|1B|1C|-4]]]]

I finally found the answer. 

Charles 3.11.2 works perfectly with WebSocket.

I use <a href="http://socket.io/" rel="noreferrer">socketIO</a>, so I've already seen http requests sent during the negotiation phase, but I missed websockets traffic.

In the beginning, socketIO try to use polling then switches to use websockets.

The websocket traffic is visible when you go to the request with status: "Sending request body" which is actually wss:// request.

You even have a dedicated tab for this kind of traffic. The rest of messages will appear right there.

<a href="https://i.stack.imgur.com/5UDaw.png" rel="noreferrer"><img src="https://i.stack.imgur.com/5UDaw.png" alt="enter image description here"></a>

PS1. Ensure you're connected to socket properly then it appears in Charles. 
PS2. I suggest using socketIO it's a great enhancement for full-duplex traffic like websockets.

blocks|key|2711546|text|客户端更新：显然Socket.IO--swift+v15.1.0现在可以正确支持SOCKS代理。我还没有尝试过，但这意味着不再需要对红蜘蛛进行这些手动编辑。|type|unstyled|depth|inlineStyleRanges|offset|length|style|BOLD|entityRanges|data|2711547|2711548|公认的答案似乎不适用于iOS设备上的Socket.IO。|2711549|最新版本的Socket.IO-Client-Swift+(撰写本文时为15.0.0)在iOS/OS上使用WebSockets的Starscream。|2711550|好消息是，红蜘蛛支持SOCKS代理：|2711551|2711552|Socket.IO不公开红蜘蛛websocket或提供任何用于启用SOCKS代理行为的应用编程接口。|ordered-list-item|2711553|内置于红蜘蛛中的SOCKS代理使用操作系统SOCKS代理设置，这些设置很难设置(至少对于iOS)。|2711554|2711555|如果我有一些时间，我可能会提出一个PR来更彻底地解决这个问题，但考虑到它需要红蜘蛛和Socket.IO-Client-Swift的工作，这并不是完全直接的。|2711556|为了临时调试的目的(这就是Charles的用例)，解决这个问题的最简单方法是将WebSocket.swift文件作为红蜘蛛的一部分进行编辑，并替换以下代码：|CODE|2711557|if+enableSOCKSProxy+{
++++let+proxyDict+=+CFNetworkCopySystemProxySettings()
++++let+socksConfig+=+CFDictionaryCreateMutableCopy(nil,+0,+proxyDict!.takeRetainedValue())
++++let+propertyKey+=+CFStreamPropertyKey(rawValue:+kCFStreamPropertySOCKSProxy)
++++CFWriteStreamSetProperty(outputStream,+propertyKey,+socksConfig)
++++CFReadStreamSetProperty(inputStream,+propertyKey,+socksConfig)
}|code-block|syntax|javascript|2711558|使用以下代码：|2711559|let+socksConfig+=+CFDictionaryCreateMutableCopy(nil,+0,+CFNetworkCopySystemProxySettings()!.takeRetainedValue())+as!+[String:+Any]
let+propertyKey+=+CFStreamPropertyKey(rawValue:+kCFStreamPropertySOCKSProxy)
let+ip+=+socksConfig["HTTPSProxy"]
let+proxySocksConfig+=+["SOCKSProxy":+ip,+"SOCKSPort":+8889,+"SOCKSEnable":+true]+as+CFDictionary+//+Where+8889+is+the+SOCKS+proxy+port+in+Charles
CFWriteStreamSetProperty(outputStream,+propertyKey,+proxySocksConfig)
CFReadStreamSetProperty(inputStream,+propertyKey,+proxySocksConfig)|2711560|这将确保默认情况下启用SOCKS代理，并通过Charles路由所有websockets流量。|2711561|然后，您需要确保在iOS中配置了HTTP代理设置(因为HTTP和SOCKS将使用相同的IP+)，在Charles中启用了SOCKS代理，并且端口与上面代码中的端口匹配(缺省为8889)。|2711562|entityMap|0|LINK|mutability|MUTABLE|url|https://github.com/daltoniam/Starscream^0|I|1O|0|0|0|S|0|0|22|1R|A|0|0|0|I|0|0|0|1E|0|0|1D|0|0|0|26|0|0|26|13|F|0|0|0|7|0|0|0|1A|0|0|2L|0^^$0|@$1|2|3|4|5|6|7|1J|8|@$9|1K|A|1L|B|C]]|D|@]|E|$]]|$1|F|3|-4|5|6|7|1M|8|@]|D|@]|E|$]]|$1|G|3|H|5|6|7|1N|8|@$9|1O|A|1P|B|C]]|D|@]|E|$]]|$1|I|3|J|5|6|7|1Q|8|@$9|1R|A|1S|B|C]]|D|@$9|1T|A|1U|1|1V]]|E|$]]|$1|K|3|L|5|6|7|1W|8|@$9|1X|A|1Y|B|C]]|D|@]|E|$]]|$1|M|3|-4|5|6|7|1Z|8|@]|D|@]|E|$]]|$1|N|3|O|5|P|7|20|8|@$9|21|A|22|B|C]]|D|@]|E|$]]|$1|Q|3|R|5|P|7|23|8|@$9|24|A|25|B|C]]|D|@]|E|$]]|$1|S|3|-4|5|6|7|26|8|@]|D|@]|E|$]]|$1|T|3|U|5|6|7|27|8|@$9|28|A|29|B|C]]|D|@]|E|$]]|$1|V|3|W|5|6|7|2A|8|@$9|2B|A|2C|B|C]|$9|2D|A|2E|B|X]]|D|@]|E|$]]|$1|Y|3|Z|5|10|7|2F|8|@]|D|@]|E|$11|12]]|$1|13|3|14|5|6|7|2G|8|@$9|2H|A|2I|B|C]]|D|@]|E|$]]|$1|15|3|16|5|10|7|2J|8|@]|D|@]|E|$11|12]]|$1|17|3|18|5|6|7|2K|8|@$9|2L|A|2M|B|C]]|D|@]|E|$]]|$1|19|3|1A|5|6|7|2N|8|@$9|2O|A|2P|B|C]]|D|@]|E|$]]|$1|1B|3|-4|5|6|7|2Q|8|@]|D|@]|E|$]]]|1C|$1D|$5|1E|1F|1G|E|$1H|1I]]]]

UPDATE: Apparently socket.io-client-swift v15.1.0 now properly supports SOCKS proxy. I have not yet tried it, but it would mean that these manual edits to Starscream are no longer required.

<hr>

The accepted answer does not seem to work with Socket.IO on iOS devices.

The latest version of Socket.IO-Client-Swift (15.0.0 at the time of writing) uses <a href="https://github.com/daltoniam/Starscream" rel="noreferrer">Starscream</a> for WebSockets on iOS/OS X.

The good news is that Starscream supports SOCKS proxying however:

<ol>
<li>Socket.IO does not expose the Starscream websocket or provide any API for enabling the SOCKS proxying behaviour.</li>
<li>The SOCKS proxying built into Starscream uses the OS SOCKS proxy settings which are cumbersome to setup (at least for iOS).</li>
</ol>

If I get some time I might propose a PR to address this more thoroughly, but given that it requires work to both Starscream and Socket.IO-Client-Swift, this is not entirely straightforward.

The easiest way to hack around this for temporary debugging purposes (which is the use case for Charles!), is to edit the <code>WebSocket.swift</code> file as part of Starscream, and replace this code:

<pre><code>if enableSOCKSProxy {
 let proxyDict = CFNetworkCopySystemProxySettings()
 let socksConfig = CFDictionaryCreateMutableCopy(nil, 0, proxyDict!.takeRetainedValue())
 let propertyKey = CFStreamPropertyKey(rawValue: kCFStreamPropertySOCKSProxy)
 CFWriteStreamSetProperty(outputStream, propertyKey, socksConfig)
 CFReadStreamSetProperty(inputStream, propertyKey, socksConfig)
}
</code></pre>

with this code:

<pre><code>let socksConfig = CFDictionaryCreateMutableCopy(nil, 0, CFNetworkCopySystemProxySettings()!.takeRetainedValue()) as! [String: Any]
let propertyKey = CFStreamPropertyKey(rawValue: kCFStreamPropertySOCKSProxy)
let ip = socksConfig["HTTPSProxy"]
let proxySocksConfig = ["SOCKSProxy": ip, "SOCKSPort": 8889, "SOCKSEnable": true] as CFDictionary // Where 8889 is the SOCKS proxy port in Charles
CFWriteStreamSetProperty(outputStream, propertyKey, proxySocksConfig)
CFReadStreamSetProperty(inputStream, propertyKey, proxySocksConfig)
</code></pre>

This will ensure the SOCKS proxy is enabled by default, and will route all the websockets traffic via Charles.

You then need to ensure that the HTTP proxy settings are configured in iOS (since the same IP will be used for both HTTP and SOCKS), SOCKS proxy is enabled in Charles, and that the port matches the port in the code above (by default 8889).

blocks|key|2711638|text|谢谢你非常非常有帮助的回答Jonathan+Ellis！我使用的是Pusher，它工作得很好！|type|unstyled|depth|inlineStyleRanges|entityRanges|data|2711639|然而，我发现socksConfig并不总是包含有效的数据，当我从那里提取IP时，它不工作或会崩溃。因为我们从那里得到的唯一东西是本地主机IP，所以我在WebSocket.swift中替换了以下内容|offset|length|style|CODE|2711640|if+enableSOCKSProxy+{
++++let+proxyDict+=+CFNetworkCopySystemProxySettings()
++++let+socksConfig+=+CFDictionaryCreateMutableCopy(nil,+0,+proxyDict!.takeRetainedValue())
++++let+propertyKey+=+CFStreamPropertyKey(rawValue:+kCFStreamPropertySOCKSProxy)
++++CFWriteStreamSetProperty(outputStream,+propertyKey,+socksConfig)
++++CFReadStreamSetProperty(inputStream,+propertyKey,+socksConfig)
}|code-block|syntax|javascript|2711641|有了这个：|2711642|let+propertyKey+=+CFStreamPropertyKey(rawValue:+kCFStreamPropertySOCKSProxy)
let+proxySocksConfig+=+["SOCKSProxy":+"127.0.0.1",+"SOCKSPort":+8889,+"SOCKSEnable":+true]+as+CFDictionary+//+Where+8889+is+the+SOCKS+proxy+port+in+Charles
CFWriteStreamSetProperty(outputStream,+propertyKey,+proxySocksConfig)
CFReadStreamSetProperty(inputStream,+propertyKey,+proxySocksConfig)|2711643|然后按照您所描述的在Charles中启用了socks代理。|2711644|再次感谢！|2711645|entityMap^0|0|6|B|23|F|0|0|0|0|0|0^^$0|@$1|2|3|4|5|6|7|W|8|@]|9|@]|A|$]]|$1|B|3|C|5|6|7|X|8|@$D|Y|E|Z|F|G]|$D|10|E|11|F|G]]|9|@]|A|$]]|$1|H|3|I|5|J|7|12|8|@]|9|@]|A|$K|L]]|$1|M|3|N|5|6|7|13|8|@]|9|@]|A|$]]|$1|O|3|P|5|J|7|14|8|@]|9|@]|A|$K|L]]|$1|Q|3|R|5|6|7|15|8|@]|9|@]|A|$]]|$1|S|3|T|5|6|7|16|8|@]|9|@]|A|$]]|$1|U|3|-4|5|6|7|17|8|@]|9|@]|A|$]]]|V|$]]

Thanks for your very very helpful answer Jonathan Ellis! 
I'm using Pusher and this worked great!

However, I found <code>socksConfig</code> to not always contain valid data and didn't work or would crash the app when I pulled the IP from there. Since the only thing we are getting from there is the localhost IP I just replaced the following in <code>WebSocket.swift</code>

<pre><code>if enableSOCKSProxy {
 let proxyDict = CFNetworkCopySystemProxySettings()
 let socksConfig = CFDictionaryCreateMutableCopy(nil, 0, proxyDict!.takeRetainedValue())
 let propertyKey = CFStreamPropertyKey(rawValue: kCFStreamPropertySOCKSProxy)
 CFWriteStreamSetProperty(outputStream, propertyKey, socksConfig)
 CFReadStreamSetProperty(inputStream, propertyKey, socksConfig)
}
</code></pre>

with this:

<pre><code>let propertyKey = CFStreamPropertyKey(rawValue: kCFStreamPropertySOCKSProxy)
let proxySocksConfig = ["SOCKSProxy": "127.0.0.1", "SOCKSPort": 8889, "SOCKSEnable": true] as CFDictionary // Where 8889 is the SOCKS proxy port in Charles
CFWriteStreamSetProperty(outputStream, propertyKey, proxySocksConfig)
CFReadStreamSetProperty(inputStream, propertyKey, proxySocksConfig)
</code></pre>

And then enabled the socks proxy in Charles as you described. 

Thanks Again!

blocks|key|34582|text|找到了一个变通的解决方案:在尝试之后，我得出结论，尽管iOS模拟器遵循HTTP的系统代理设置，但没有遵循WebSocket。也不遵循Socks5代理设置。但是，我们可以在Charles中使用Reverse+Proxies来强制模拟器使用它。在Charles中，单击Proxy+->+Reverse+Proxies，设置一个本地地址作为您的WebSocket服务器的透明代理，然后在new+WebSocket(<address>)中使用该地址(在React+Native中很好)，然后您可以在Charles中看到您的WebSocket连接|type|unstyled|depth|inlineStyleRanges|offset|length|style|BOLD|CODE|entityRanges|data|34583|entityMap^0|Z|4|1G|9|2N|F|3O|O|5A|O|0^^$0|@$1|2|3|4|5|6|7|I|8|@$9|J|A|K|B|C]|$9|L|A|M|B|C]|$9|N|A|O|B|D]|$9|P|A|Q|B|D]|$9|R|A|S|B|D]]|E|@]|F|$]]|$1|G|3|-4|5|6|7|T|8|@]|E|@]|F|$]]]|H|$]]

Found a workaround solution:
After trying, I conclude that although iOS simulators follow system proxy settings for HTTP, WebSocket is not followed. Socks5 proxy settings is not followed, either.
However, we can use <code>Reverse Proxies</code> in Charles to force the simulator to use it.
In Charles, click <code>Proxy -&gt; Reverse Proxies</code>, set up a local address to be your WebSocket server's transparent proxy, then use that address in your <code>new WebSocket(&lt;address&gt;)</code> (Well in the case of React Native), then you can see your WebSocket connections appear in Charles

I would like to inspect network traffic going through web sockets, I have no control over the networking code as this is a binary lib for which I do not have the source code, so I cannot do any log/breakpoint in the networking part of the code.

I have tried using the latest version of CharlesProxy which claim to be able to sniff websockets however when I tried the url and apis using websockets were not even mentionned in the list of endpoints called from my iPhone.

<a href="https://i.stack.imgur.com/x6APp.png"><img src="https://i.stack.imgur.com/x6APp.png" alt="Version 3.11 release notes"></a>

I have verified that CharlesProxy is configured correctly as I am able to inspect non-websocket traffic even under SSL.

So my question is: did anyone find a solution to inspect traffic going through websockets with CharlesProxy?

Note: I have ATS disabled when using iOS9

Thanks!

How to inspect websocket traffic with charlesproxy for iOS simulator/devices

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

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

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

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

文章

问答

视频

学习中心

腾讯云实验室

直播

竞赛

腾讯云代码分析专区

腾讯iOA零信任安全管理系统专区

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

腾讯云数据库专区

腾讯云顾问专区

腾讯云原生专区

腾讯混元专区

腾讯云TCE专区

腾讯云Lighthouse专区

腾讯云HAI专区

腾讯云Edgeone专区

腾讯云存储专区

腾讯云智能专区

腾讯轻联专区 

腾讯云开发专区

TAPD专区

腾讯轻量云游戏服专区

腾讯云最具价值专家

腾讯云架构师技术同盟

腾讯云创作之星

腾讯云开发者先锋 

腾讯云代码助手

CODING DevOps

Cloud Studio

SDK中心

API中心

命令行工具

我想检查通过网络套接字的网络流量，我没有控制网络代码，因为这是一个二进制的库，我没有源代码，所以我不能做任何日志/断点在网络部分的代码。我已经尝试使用最新版本的CharlesProxy，它声称能够嗅探websockets，但是当我尝试使用websockets的url和apis时，从我的iPhone调用的端点列表中甚至都...

问如何使用charlesproxy为iOS模拟器/设备检查websocket流量
EN

Stack Overflow用户

社区

活动

圈层

关于

腾讯云开发者

热门产品

热门推荐

更多推荐

问如何使用charlesproxy为iOS模拟器/设备检查websocket流量EN