www.ebay.com - see bug description

[webcompat-bot]

URL: https://www.ebay.com/itm/Lenovo-E20-WorkStation-Desktop-Computer-Tower-Core-i3-8GB-500GB-Windows-10-Pro/253610693959?_mwBanner=1

Browser / Version: Firefox Mobile (Tablet) 63.0
Operating System: Android 7.0
Tested Another Browser: Yes

Problem type: Something else
Description: it will not load the site and wifi is on
Steps to Reproduce:

From webcompat.com with ❤️

[kbrosnan]

sounds like a dupe of #18128

[softvision-sergiulogigan]

Hmmm... I don't think so...

On Firefox Nightly, we get

While on Chrome,

Tested on Firefox Nightly 63, on Huawei P10 (Android 8.0) - 1080 x 1920 pixels (~432 ppi pixel density) and on Nexus 9 (Android 6.0.1) - 1536 x 2048 pixels, 4:3 ratio (~281 ppi density).

[denschub]

Yes, there is some ping-ponging going on. However, this is entirely server-side based on the User Agent:

$ curl -H "User-Agent: Mozilla/5.0 (Android 9; Mobile; rv:63.0) Gecko/63.0 Firefox/63.0" -I "https://www.ebay.com/itm/Lenovo-E20-WorkStation-Desktop-Computer-Tower-Core-i3-8GB-500GB-Windows-10-Pro/253610693959?_mwBanner=1"
HTTP/2 301
location: https://m.ebay.com/itm/Lenovo-E20-WorkStation-Desktop-Computer-Tower-Core-i3-8GB-500GB-Windows-10-Pro/253610693959?_mwBanner=1&_rdt=1

$ curl -H "User-Agent: Mozilla/5.0 (Android 9; Mobile; rv:63.0) Gecko/63.0 Firefox/63.0" -I "https://m.ebay.com/itm/Lenovo-E20-WorkStation-Desktop-Computer-Tower-Core-i3-8GB-500GB-Windows-10-Pro/253610693959?_mwBanner=1&_rdt=1"
HTTP/1.1 302 Found
Location: https://www.ebay.com/itm/0?_mwBanner=1&_rdt=1

$ curl -H "User-Agent: Mozilla/5.0 (Android 9; Mobile; rv:63.0) Gecko/63.0 Firefox/63.0" -I "https://www.ebay.com/itm/0?_mwBanner=1&_rdt=1"
HTTP/2 301
location: https://m.ebay.com/itm/0?_mwBanner=1&_rdt=1

$ curl -H "User-Agent: Mozilla/5.0 (Android 9; Mobile; rv:63.0) Gecko/63.0 Firefox/63.0" -I "https://m.ebay.com/itm/0?_mwBanner=1&_rdt=1"
HTTP/1.1 302 Found
Location: https://www.ebay.com/itm/0?_mwBanner=1&_rdt=1

The last two redirect generate a endless loop here. It works fine with Chrome's user agent, so there seems to be a disagreement about whether Fenenc is a mobile browser or not. As GoFaster is not yet in Fennec, there is nothing we can really do to hotfix that (except for spinning a one-off addon and having that pushed to release). Given we have direct channels, outreach is probably the better way.

Ping @miketaylr.

---

[denschub]

This might be related to #18128 and the fact that there was some outreach happening yesterday.

[softvision-sergiulogigan]

Just that in #18128 there is a "Desktop site instead of Mobile site" issue investigated, because @softvision-oana-arbuzov did not see the issue we are seeing today.

[denschub]

The reason I think there is a link between the issues is the fact that we get redirected back and forth between the desktop and mobile versions. It almost looks like the servers delivering the desktop versions are aware of Fenenc being a mobile browser, while the mobile servers are not, so they are redirecting back to desktop.

I followed up on the mailing list thread, so at least they should be aware.

[kbrosnan]

The reason I mentioned 18128 is that the first comment directly matches this issue.

Description: ''site is not redirecting properly''

It was morphed when Oana commented that she gets the desktop site.

[adamopenweb]

Duplicate: https://bugzilla.mozilla.org/show_bug.cgi?id=1482927

[miketaylr]

Let's send an override for now: https://bugzilla.mozilla.org/show_bug.cgi?id=1483233

[softvision-oana-arbuzov]

The issue has been fixed.

Tested with:
Browser / Version: Firefox Nightly 68.0a1 (2019-06-10)
Operating System: Sony Xperia Z2 (Android 6.0.1) - 1080 x 1920 pixels (~424 ppi pixel density)