-
Notifications
You must be signed in to change notification settings - Fork 4
Missing country code for some users #482
Comments
This isn't happening on Cats Gone Good (which is roughly the exact same codebase):
Admittedly, Cats Gone Good only has 71 test users. But perhaps an indication that it could be a server or Fastly configuration issue? |
Running the same query on Athletes Gone Good shows only 145 (of 53,924) users without a |
And logs are coming in after deploying #486 to production:
Not seeing any patterns so far... but it's definitely still having trouble. |
For anyone following along, @sheyd is checking in with Fastly support now. ☎️ |
Just to be extra sure that this isn't due to a bug in the application, I tried adding some logging directly to the top of error_log($_SERVER['HTTP_X_FASTLY_COUNTRY_CODE'].', ', 3, '/home/dosomething/test.log'); Here’s the logged country codes over the course of roughly 5 minutes:
My best guess (and I believe @sheyd's as well) is that Fastly just plain isn’t sending those country codes for a random selection of requests, perhaps due to a misconfigured server somewhere in their network. |
Another interesting thing, which may be a clue to what's going on... request logs on Cats Gone Good show what seems to be the individual request's IP address whereas Celebs Gone Good consistently shows the exact same (internal?) IP address for every single request: Perhaps something in between (HAProxy, Varnish, ...?) is stripping out the header from time to time? /cc @sheyd |
For what it's worth, there's still no instances of a missing country code on Cats Gone Good (although of course it gets drastically less traffic). Just for fun, I tried targeting a loader.io test at Cats Gone Good, and all requests properly logged their country code. |
Some users don't seem to be getting their country code applied correctly (being shown "global" experience, even from the US) and getting
null
saved to their country code field.Not able to consistently reproduce, and continuing to investigate. 🔍
The text was updated successfully, but these errors were encountered: