Login to start a new topic

decode not working

Hi there,


I'm using the latest fiddler everywhere on Ubuntu 18.04.4 LTS. I'm trying to see the decoded response body in `Inspectors > Response > Raw`, however I only seem to get encoded versions. I can't quite figure out what encoding it is from the view - it does seem to be decompressed, but there are a few extra non-ascii chars in there which make it hard to read. Example below:


- GET https://whitelabel.spikedata.co.za/ HTTP/1.1


- actual response body:

{"message":"Required authorization token is missing or invalid"}


- response in fiddler:


Date: Mon, 10 Aug 2020 09:31:47 GMT

Content-Type: application/json; charset=utf-8

Transfer-Encoding: chunked

Connection: keep-alive

X-Powered-By: Express

X-Frame-Options: sameorigin

Content-Security-Policy: frame-ancestors 'self'

ETag: W/"40-3ttzq8UwAG/P4XNbV2q8xjg0Qcw"

CF-Cache-Status: DYNAMIC

cf-request-id: 04794f449e000047f711983200000001

Expect-CT: max-age=604800, report-uri="https://report-uri.cloudflare.com/cdn-cgi/beacon/expect-ct"

Server: cloudflare

CF-RAY: 5c08b4b43a5a47f7-CPT

Content-Encoding: br


40

!��� �T߮D%

ٟ]��)8���V�0�\�

8�$h��WE5��ƾ�@���3���X8sI���

0


If possible please post the problematic session as a SAZ archive (you can use the export functionality) so we could investigate further. Currently. the request to the linked URL is working as expected on our side (but we are not seeing any encoding being used from the server so it looks that something has changed)

Hi Nick,

Thanks for the response. It looks like its a bug with:

  • `Content-Encoding: br`
  • https
  • Ubuntu 18 client in combination with the above (I don't have another machine to try it on atm)

I'm running the Ubuntu 18 fiddler everywhere client and can confirm that (http, no br) works, (https, with br) doesn't.
See attached .saz with 3 requests




saz

Thank you for providing the endpoints. I can confirm that this looks like a legit bug, and the BR content encoding is also not being encoded on my side. Logging this one as a bug (but it could be a feature request to support BR encoding), and once the issue is discussed in our planning meetings, I will update the information here.

Login to start a new topic