Provide ways to inspect the compressed payload [40720400]

Feature Request

Status Update

No update yet.

Description

vi...@gmail.com

created issue #1

Sep 18, 2020 09:14AM

UserAgent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10_14_6) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/85.0.4183.102 Safari/537.36

Steps to reproduce the problem:
1. Compress the XHR/Fetch POST payload using the new Compression Stream spec -

https://wicg.github.io/compression/
2. Open the browser devtools and look at the Request Payload
3. The payload shown is a compressed one, which is not so useful for debugging

What is the expected behavior?
With the new Compression Stream specification -

https://wicg.github.io/compression/, JavaScript developers have the ability to reduce the payload size by applying compression to all the outgoing requests. Curently, the browser devtools is less helpful when it comes to debugging the payload when its compressed using the stream API.

It would be great if the browser devtools provides a way to debug/inspect the request payload which would make the life of devs easier.

What went wrong?
Nothing went wrong, its a new feature request

Did this work before? N/A

Chrome version: 85.0.4183.102 Channel: stable
OS Version: OS X 10.14.6
Flash Version:

uncompressed-request.png

377 KB

View

Download

Comments

sa...@chromium.org <sa...@chromium.org> #2Sep 20, 2020 04:32PM

I notice the same issue and LogCat shows the following message:
Google Play services out of date. Requires 3159100 but found 3136130

va...@chromium.org <va...@chromium.org> #3Sep 21, 2020 07:26AM

Same here.

"Google Play services out of date. Requires 3159100 but found 3136130"

ma...@chromium.org <ma...@chromium.org> #4Sep 21, 2020 09:29AM

me as well....
Google Play services out of date. Requires 3159100 but found 3136130

vi...@gmail.com <vi...@gmail.com> #5Nov 6, 2020 03:22PM

I was hopeful that the release of API 18 (4.3) would have created a solution to this, unfortunately it includes version 3158130

pe...@chromium.org <pe...@chromium.org> #6Mar 23, 2021 03:26AM

Having the same issue:

07-25 00:03:54.998: W/GooglePlayServicesUtil(27293): Google Play services out of date. Requires 3159100 but found 3158130

te...@elastic.co <te...@elastic.co> #7Mar 10, 2022 09:27AM

same

ha...@google.com <ha...@google.com> #8Jan 9, 2024 02:09AM

SAME ! - Google can't do sth working in 100 percent?

is...@google.com <is...@google.com> #9Jan 9, 2024 02:09AM

same issue - Google Play services out of date. Requires 3159100 but found 3158130

pe...@google.com <pe...@google.com> #10Dec 11, 2024 03:37PM

Having the same issure:

07-26 03:14:00.731: W/GooglePlayServicesUtil(2566): Google Play services out of date. Requires 3159100 but found 3136130

pe...@google.com <pe...@google.com> #11Dec 12, 2024 03:38PM

API 18 (4.3) same issue
07-26 03:54:03.303: W/GooglePlayServicesUtil(1207): Google Play services out of date. Requires 3159100 but found 3158130

IssueTracker

This issue is a part of the Chromium tracker.