addons.mozilla.org is staged behind 220.127.116.11 in Amsterdam. Bug for tracking deployment.
mrz, what timeframe (realistically) would you need this by?
Best case next week. Worst case by the end of the month - it's tied into a Q3 goal.
Just started testing this, found a bug: 1. Load https://addons.mozilla.org/en-US/firefox/ 2. Click on "Log in", which loads https://addons.mozilla.org/en-US/firefox/users/login?to=en-US%2Ffirefox%2F 3. Log in 4. You're now returned to https://addons.mozilla.org/en-US/firefox/, but it's not reflecting the logged-in status, until you force a hard-refresh
oremj, cookie caching?
i goofed - didn't apply any of the cache rules in amsterdam. donner, test again?
(In reply to comment #5) > i goofed - didn't apply any of the cache rules in amsterdam. donner, test > again? I can still reproduce comment 3 -- it's not too soon to try, right? I can work with you tomorrow (today, really!) on this.
I think this should work now. Make sure you clear your browser cache.
(In reply to comment #7) > I think this should work now. Make sure you clear your browser cache. This is working fine, and I tested uploading an add-on, too; good to go from QA.
I just commented on bug 515295 comment #4 regarding log files. The dependency chain for that bug is convoluted so I want to make sure the question gets answered before we go live.
This is live. To revert, change DNS to 18.104.22.168.
Verified FIXED -- it's hot.