Поиск в Поддержке

Избегайте мошенников, выдающих себя за службу поддержки. Мы никогда не попросим вас позвонить, отправить текстовое сообщение или поделиться личной информацией. Сообщайте о подозрительной активности, используя функцию «Пожаловаться».

Learn More

Firefox developer tools response garbarge

  • 4 ответа
  • 1 имеет эту проблему
  • 72 просмотра
  • Последний ответ от george1319

more options

Hi, I'm having an issue with Firefox developer tools response in the network tab. When I look at the response it's all garbage but when I look at it in Chrome or Charles proxy it looks fine.

To replicate: 1. Go to https://www.realestate.com.au/new-homes/ 2. Open up developer tools, switch to network tab and filter by .mst 2. On the webpage click `Explorer` sub menu item 3. Inspect the response of the .mst requests and it's garbage like: PHN0eWxlIHR5cGU9InRleHQvY3NzIj4uc3RhbmRhcmRfX3N0YW5kYXJkLWNvbnRhaW5lcl9fXzFGVFJ3e21heC13aW

Hi, I'm having an issue with Firefox developer tools response in the network tab. When I look at the response it's all garbage but when I look at it in Chrome or Charles proxy it looks fine. To replicate: 1. Go to https://www.realestate.com.au/new-homes/ 2. Open up developer tools, switch to network tab and filter by .mst 2. On the webpage click `Explorer` sub menu item 3. Inspect the response of the .mst requests and it's garbage like: PHN0eWxlIHR5cGU9InRleHQvY3NzIj4uc3RhbmRhcmRfX3N0YW5kYXJkLWNvbnRhaW5lcl9fXzFGVFJ3e21heC13aW
Приложенные скриншоты

Выбранное решение

This isn't garbage, but Firefox shows the response encoded as base64 to avoid issues with characters that can't be displayed:

PHN0eWxlIHR5cGU9InRleHQvY3NzIj4uc3RhbmRhcmRfX3N0YW5kYXJkLWNvbnRhaW5lcl9fXzFGVFJ3e21heC13aW

decoded via atob('PHN0eWxlIHR5cGU9InRleHQvY3NzIj4uc3RhbmRhcmRfX3N0YW5kYXJkLWNvbnRhaW5lcl9fXzFGVFJ3e21heC13aW') this becomes:

<style type="text/css">.standard__standard-container___1FTRw{max-wi
Прочитайте этот ответ в контексте 👍 0

Все ответы (4)

more options

Выбранное решение

This isn't garbage, but Firefox shows the response encoded as base64 to avoid issues with characters that can't be displayed:

PHN0eWxlIHR5cGU9InRleHQvY3NzIj4uc3RhbmRhcmRfX3N0YW5kYXJkLWNvbnRhaW5lcl9fXzFGVFJ3e21heC13aW

decoded via atob('PHN0eWxlIHR5cGU9InRleHQvY3NzIj4uc3RhbmRhcmRfX3N0YW5kYXJkLWNvbnRhaW5lcl9fXzFGVFJ3e21heC13aW') this becomes:

<style type="text/css">.standard__standard-container___1FTRw{max-wi

Изменено cor-el

more options

Thanks. Yep. I thought it might be encoded. I should have checked that. Is there a way to get the dev tools to show the response as unencoded text? Is it showing it as base64 because of the content-type `application/octet-stream`? I'm just trying to understand why it's different to html or text response for example.

more options

Yes, that is quite likely the cause as this application/octet-stream content-type can be used for all kind of data. I do not get .mst files when I visit your link, so I can't check its initiator. You will also see the response being encoded for (woff) font files. HTML files and image files are among the content that is rendered.

more options

Thanks. You need to click the Click the `explore` sub menu to get .mst files. See in my screenshot