如何解密Firebase对app-measurement.com的请求 [英] How to decrypt Firebase requests to app-measurement.com

问题描述

我们注意到我们的iOS应用正在将请求发送到 http://app-measurement.com .主体似乎被加密或压缩了

We noticed that our iOS app is sending requests to http://app-measurement.com. The body seems to be encrypted or compressed though

:method: POST
:scheme: https
:path: /a
:authority: app-measurement.com
accept: */*
content-type: application/x-www-form-urlencoded
content-encoding: gzip
accept-language: en-gb
content-length: 371
accept-encoding: br, gzip, deflate


 ;

_uwa

_pfoq


_oauto

_r

_c_fݶ- 
...

我已经检查了它是否是gzip，但事实并非如此.

I already checked if it's gzip but that doesn't seem to be it.

有人知道如何解密才能看到请求内容吗?

Does anyone know how to decrypt this to be able to see the request content?

推荐答案

firebaser此处

此请求是Google Analytics for Firebase的一部分，用于报告来自客户端的分析事件.它经过高度压缩以最大程度地减少带宽使用.

This request is part of Google Analytics for Firebase to report the analytics events from the client. It is heavily compressed to minimize the bandwidth usage.

没有API可以查看请求的原始内容，但是您可以在此处找到有关所收集数据的更多信息:

There is no API to see the raw contents of the request, but here is where you can find more on the data collected:

1. 自动收集的事件上的文档自动收集的用户属性.
2. BigQuery架构是一个很好的表示形式收集的信息(尽管在某些情况下，它还包括一些添加到服务器上的字段，例如位置信息和流量来源).
3. 设备日志(例如logcat)公开了我们记录的事件/参数.

1. The documentation on auto-collected events and auto collected user properties.
2. The BigQuery schema is a pretty good representation of what we collect (although this also includes some fields which are added on the server, like location information and traffic source, in some cases).
3. Device logs (e.g. logcat) expose the events/parameters we log.

这篇关于如何解密Firebase对app-measurement.com的请求的文章就介绍到这了，希望我们推荐的答案对大家有所帮助，也希望大家多多支持IT屋！