Last modified: 2014-02-12 23:54:09 UTC

Wikimedia Bugzilla is closed!

Wikimedia migrated from Bugzilla to Phabricator. Bug reports are handled in Wikimedia Phabricator.
This static website is read-only and for historical purposes. It is not possible to log in and except for displaying bug reports and their history, links might be broken. See T59934, the corresponding Phabricator task for complete and up-to-date bug report information.
Bug 57934 - Search not working for mobile over http for Firefox on test2wiki
Search not working for mobile over http for Firefox on test2wiki
Status: RESOLVED FIXED
Product: MobileFrontend
Classification: Unclassified
stable (Other open bugs)
unspecified
All All
: Unprioritized normal
: ---
Assigned To: Arthur Richards
: browser-test-bug
Depends on:
Blocks:
  Show dependency treegraph
 
Reported: 2013-12-03 17:55 UTC by Chris McMahon
Modified: 2014-02-12 23:54 UTC (History)
10 users (show)

See Also:
Web browser: Firefox
Mobile Platform: ---
Assignee Huggle Beta Tester: ---


Attachments

Description Chris McMahon 2013-12-03 17:55:20 UTC
Seen in Firefox:

http://test2.m.wikipedia.org/wiki/Main_Page or http://test2.m.wikipedia.org/wiki/Main_Page?useformat=mobile

Type 'bara' into the search box. 

Barack Obama page suggestion should appear, but page says explicitly that no results are found.

Search works correctly from https:  https://test2.m.wikipedia.org

Notes: 

* Search works correctly on beta labs from http URL http://en.m.wikipedia.beta.wmflabs.org/wiki/Main_Page?useformat=mobile

* Search works correctly in production from http URL http://en.m.wikipedia.org

* http://test2.m.wikipedia.org redirects to https for Chrome (and search works correctly) but not for Firefox
Comment 1 Bingle 2013-12-03 17:56:28 UTC
Prioritization and scheduling of this bug is tracked on Mingle card https://wikimedia.mingle.thoughtworks.com/projects/mobile/cards/1477
Comment 2 Jon 2013-12-03 18:15:41 UTC
Interestingly searching for "Bara" works but "bara" doesn't.

http://test2.m.wikipedia.org/w/api.php?format=json&search=bara&action=opensearch&namespace=0&limit=15
On Firefox returns ["bara",[]] in response
On Chrome returns ["bara",["Barack Obama"]] in response

Why would the response differ on user agent?! This is server side!?!
Comment 3 Chris McMahon 2013-12-03 20:17:03 UTC
also see this issue at at https://m.mediawiki.org for both Firefox/http and Chrome/https
Comment 4 Nik Everett 2013-12-03 20:41:21 UTC
I had a look at this and it is certainly not caused by cirrussearch.

I know it isn't caused by CirrusSearch because digging into this caused me to see that Cirrus isn't enabled _anywhere_.  This is a mistake and we'll get it back enabled on test2wiki in a bit.

It does seem to be specific to the word "bara" though.  "bar" and "barac" both find him.  This could be complicated by caching.....
Comment 5 Arthur Richards 2013-12-04 01:40:12 UTC
After chatting a bit with Nik in IRC, I'm becoming more convinced this is a caching issue. I'm able to replicate the OP's issue in firefox as a logged out user, but if I log in, search behaves as expected. When I log out and try to search, things work as expected (presumably caching is varied on one, some or all of the cookies that linger after logging out).

I looked at the network requests, and sure enough the failing 'bara' search string results in a cache hit while the others result in a miss. So likely an error or otherwise bad result got stuck in the cache.

Chris, what search term(s) did you try on mediawiki.org?
Comment 6 Jon 2013-12-04 18:47:51 UTC
Arthur is looking into this so marking as assigned.
Comment 7 Arthur Richards 2013-12-04 19:20:01 UTC
I feel like we can safely close this - the OP issue appears to be gone. I just tried and could no longer replicate with 'bara'. Iirc the cache entry expired Dec 4 ~1800 GMT. New response headers from 'bara' search show cache entry refreshed Dec 4 ~1900 GMT and expires Dec 5 ~1900GMT. I have a high level of confidence that a bad response/error was cached and was causing the problem. Marking as closed but feel free to reopen if issue resurfaces.

Note You need to log in before you can comment on or make changes to this bug.


Navigation
Links