Open Bug 1666804 Opened 2 years ago Updated 6 months ago

QR code of WhatsApp web app doesn't load if HTTP proxy address is specified for all proxy fields incl. SOCKS5

Categories

(Core :: Networking, defect)

Firefox 81
defect

Tracking

()

UNCONFIRMED

People

(Reporter: mikhail.kovalev, Unassigned, NeedInfo)

References

Details

Attachments

(1 file)

5.70 MB, application/octet-stream
Details

User Agent: Mozilla/5.0 (Windows NT 10.0; Win64; x64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/85.0.4183.102 Safari/537.36

Steps to reproduce:

I specified HTTP/HTTPS proxy address for all possible protocol (HTTP, HTTPS, FTP, SOCKS5).

Actual results:

QA code on the website https://web.whatsapp.com/ doesn't load

Expected results:

QA code should load. And it does load if SOCKS5 proxy is not specified.

This setup was working in Firefox 68esr. So most likely it got broken when the checkbox "Use http proxy for other protocol" got renamed to "Use http proxy for HTTPS and FTP" and socks proxy was not defined by this checkbox any longer

Bugbug thinks this bug should belong to this component, but please revert this change in case of error.

Component: Untriaged → Networking
Product: Firefox → Core

QR code, not QA code. sorry

Summary: QA code of WhatsApp web app doesn't load if HTTP proxy address is specified for all proxy fields incl. SOCKS5 → QR code of WhatsApp web app doesn't load if HTTP proxy address is specified for all proxy fields incl. SOCKS5

Can you gather some HTTP logs for us?
https://developer.mozilla.org/en-US/docs/Mozilla/Debugging/HTTP_logging

Also, if you can, confirming the commit that introduced this bug would be really useful:
https://mozilla.github.io/mozregression/quickstart.html

Flags: needinfo?(mikhail.kovalev)

I do no have time for this now, but I will provide the information next week or so.

Can you gather some HTTP logs for us?
https://developer.mozilla.org/en-US/docs/Mozilla/Debugging/HTTP_logging

Also, if you can, confirming the commit that introduced this bug would be really useful:
https://mozilla.github.io/mozregression/quickstart.html

I did some bisection tests with nightly builds (didn't go into testing individual commits).

Working build:
app_name: firefox
build_date: 2019-09-25
build_file: C:\Users\Administrator.BITBOX.mozilla\mozregression\persist\2019-09-25--mozilla-central--firefox-71.0a1.en-US.win64.zip
build_type: nightly
build_url: https://archive.mozilla.org/pub/firefox/nightly/2019/09/2019-09-25-21-56-53-mozilla-central/firefox-71.0a1.en-US.win64.zip
changeset: 15ffd69c83be752a28fc40a5db6b6859452fa41f
pushlog_url: https://hg.mozilla.org/mozilla-central/pushloghtml?fromchange=15ffd69c83be752a28fc40a5db6b6859452fa41f&tochange=c9c63f8447027d14ec2c541e82aae1014f08f812
repo_name: mozilla-central
repo_url: https://hg.mozilla.org/mozilla-central

Broken build:
app_name: firefox
build_date: 2019-09-26
build_file: C:\Users\Administrator.BITBOX.mozilla\mozregression\persist\2019-09-26--mozilla-central--firefox-71.0a1.en-US.win64.zip
build_type: nightly
build_url: https://archive.mozilla.org/pub/firefox/nightly/2019/09/2019-09-26-21-35-42-mozilla-central/firefox-71.0a1.en-US.win64.zip
changeset: 1d189ae70326e415f8590e3aeee24885fb8418bc
pushlog_url: https://hg.mozilla.org/mozilla-central/pushloghtml?fromchange=15ffd69c83be752a28fc40a5db6b6859452fa41f&tochange=1d189ae70326e415f8590e3aeee24885fb8418bc
repo_name: mozilla-central
repo_url: https://hg.mozilla.org/mozilla-central

I am attaching a log file from Firefox 81.0.1

Flags: needinfo?(mikhail.kovalev)

Based on the regression range I suspect this is caused by bug 1577862

See Also: → 1577862

Valentin, do you have time to work on this?
If not, feel free to bounce back.

Flags: needinfo?(valentin.gosu)

ni myself to have a look.

Flags: needinfo?(valentin.gosu) → needinfo?(kershaw)
You need to log in before you can comment on or make changes to this bug.