Here's the scenario (for me at least). 1. Install a proxy (I use TunnelBear). 2. Set the proxy to the UK. 3. Start Firefox and create a new profile. 4. Run a search. Notice that the Google code is missing. 6. Restart the browser. 7. Run a search Google code is there. Looking at all the search logging, we are definitely grabbing google.xml and doing the right thing per absearch. So we're not sure why on first run we don't have the code.
I tried (without proxy but I'm based in France) and couldn't reproduce. Google was the default and my very first search request on the new profile had a correct Google code. There's probably a missing step to reproduce.
I can recreate consistently with a proxy, so I'm going to debug to see if we're hitting the 2 second timeout.
Come to find out, investigation had already been done in raising the geoip timeout, but the code has never been changed. Mconnnor thought maybe we really don't need to have the timeout at all, since most people won't have interacted with search even with a long timeout, but I'll open a separate bug for that.
Status: NEW → RESOLVED
Last Resolved: 2 years ago
Resolution: --- → DUPLICATE
Duplicate of bug: 1123972
You need to log in before you can comment on or make changes to this bug.