Closed Bug 1076439 Opened 10 years ago Closed 9 years ago

Requesting a mobile google+ page returns 404

Categories

(Web Compatibility :: Site Reports, defect)

Firefox 32
All
Android
defect
Not set
normal

Tracking

(Not tracked)

RESOLVED FIXED

People

(Reporter: mcomella, Assigned: karlcow)

References

()

Details

(Whiteboard: [country-all] [serversniff] [contactready])

1) Navigate to http://dmvresistance.org
2) Click the "DMV Resistance Community" link

Expected: Mobile Google+ opens
Actual: 404

Using phony to change users agents (after clicking the link) and then refreshing, Firefox for Android and Firefox OS give 404s but Android phone, iPhone, and any non-mobile browser load correctly.

Running "stable", presumably FF 32.

Reported by :nemo on irc (CC'd).
Looks good. FWIW, Google Plus is the one redirecting to the mobile page that 404s only with a Firefox UA.
Switching UA to iPhone/Android and refreshing the mobile URL they redirect you to renders nicely, without any visible change in the URL.
So does "request desktop site" which redirects to the non-mobile page.
I can reproduce this on Alcatel One Touch (Android 4.1.2) and Samsung Galaxy S5 (Android 4.4.) on latest nightly (01-10-2014). Clicking the "DMV Resistance Community" link redirects you to the "404. That's an error". Google + page is displayed by going to Settings -> Request Desktop Site.
Component: General → Mobile
Product: Firefox for Android → Tech Evangelism
$ curl -ILA "Mozilla/5.0 (Android; Mobile; rv:32.0) Gecko/32.0 Firefox/32.0" https://plus.google.com/communities/103349576921336760265

HTTP/1.1 302 Moved Temporarily
Content-Type: text/html; charset=UTF-8
Set-Cookie: NID=67=WATIpMa3NYMorVj725YVLphEjRpp3ofGRdk61JEsYunNlv8o3_4AL6j1VW-LkTN36iaFtQsWpLYvtnlZk5HdZb7VMOAkDwGvma1sdeHJlp58MeLqFqL2xL8iFzfDDLPW;Domain=.google.com;Path=/;Expires=Fri, 03-Apr-2015 14:20:22 GMT;HttpOnly
P3P: CP="This is not a P3P policy! See http://www.google.com/support/accounts/bin/answer.py?hl=en&answer=151657 for more info."
Cache-Control: no-cache, no-store, max-age=0, must-revalidate
Pragma: no-cache
Expires: Fri, 01 Jan 1990 00:00:00 GMT
Date: Thu, 02 Oct 2014 14:20:22 GMT
Location: https://plus.google.com/app/basic/communities/103349576921336760265
X-Content-Type-Options: nosniff
X-Frame-Options: SAMEORIGIN
X-XSS-Protection: 1; mode=block
Server: GSE
Transfer-Encoding: chunked

HTTP/1.1 404 Not Found
Cache-Control: no-cache, no-store, max-age=0, must-revalidate
Pragma: no-cache
Expires: Fri, 01 Jan 1990 00:00:00 GMT
Date: Thu, 02 Oct 2014 14:20:22 GMT
Content-Type: text/html; charset=UTF-8
X-Content-Type-Options: nosniff
X-Frame-Options: SAMEORIGIN
X-XSS-Protection: 1; mode=block
Server: GSE
Transfer-Encoding: chunked
Status: UNCONFIRMED → NEW
Ever confirmed: true
Nice, and yeah, that 2nd URL is the mobile site which has different UA behaviour:

curl -ILA "Mozilla/5.0 (iPhone; CPU iPhone OS 6_0 like Mac OS X)" https://plus.google.com/app/basic/communities/103349576921336760265
fetches a page
as does
curl -ILA "Mozilla/5.0 (Linux; Android 4.1; Galaxy Nexus Build/JRN84D) AppleWebKit/535.19 (KHTML, like Gecko) Chrome/18.0.1025.166 Mobile Safari/535.19 " https://plus.google.com/app/basic/communities/103349576921336760265
(different headers tho)


while
curl -ILA "Mozilla/5.0 (Android; Mobile; rv:32.0) Gecko/32.0 Firefox/32.0" https://plus.google.com/app/basic/communities/103349576921336760265
404s
as does
curl -ILA "Mozilla/5.0 (Mobile; rv:18.0) Gecko/18.0 Firefox/18.0" https://plus.google.com/app/basic/communities/103349576921336760265

aaaand for that matter
curl -ILA "Hi. I am a browser." https://plus.google.com/app/basic/communities/103349576921336760265
also 404s.
User Story: (updated)
And, I'm sure this surprised no one at all, but sure enough, it seems all google plus communities are blocked from firefox mobile   Tried a few random ones using curl.  Worked w/ Chrome/iPhone UA, blocked with Firefox.  (oups, used wrong text field, sorry. moved)
User Story: (updated)
Assignee: nobody → kdubost
Whiteboard: [country-all] [serversniff] [contactready]
See Also: → 928074
With a Firefox Android build with version number. This is working.
Status: NEW → RESOLVED
Closed: 9 years ago
Resolution: --- → FIXED
Product: Tech Evangelism → Web Compatibility
Component: Mobile → Site Reports
You need to log in before you can comment on or make changes to this bug.