Both of these are currently returning 404 Not Found. What's up with that?
Add a comment
|
3 Answers
StackAuth's new DNS record is propagating, expect some outages as per the blog.
We expect all the DNS issues to shake out well before the recommend /sites cache time elapses.
Associated accounts on the sites themselves will be kind of weird while that record is propagating, so /users/{id}/associated wouldn't really be reliable even if you could get to it.
-
I hope so... I might have to manually patch StackMobile's cache - since it refreshes in a few minutes.Nathan Osman– Nathan Osman2010-10-24 19:34:30 +00:00Commented Oct 24, 2010 at 19:34
-
I checked out my code and I noticed that I'm using stackauth.com/sites without 1.0 (Not affected by the DNS change).. What's the difference?systempuntoout– systempuntoout2010-10-25 06:37:06 +00:00Commented Oct 25, 2010 at 6:37
-
1@systempuntoout -
/sitesbasically snuck in when we froze 1.0. There are enough people using it that we can't track down (at least, not without alot of log parsing pain) that I didn't want to just tear it out. The correct way to use the 1.0 API is to hit/1.0/sitesdirectly, we make no guarantees about the lifetime of the raw/sitesroute.Kevin Montrose– Kevin Montrose2010-10-25 06:40:21 +00:00Commented Oct 25, 2010 at 6:40
It has been more than 12 hours since I checked http://stackauth.com/1.0/sites, it is still returning a 404. Does anyone have an idea when http://stackauth.com/1.0/sites will be available?
-
I was just going to ask this myself :PNathan Osman– Nathan Osman2010-10-24 22:16:41 +00:00Commented Oct 24, 2010 at 22:16
-
Seems to be working for me nowFelix– Felix2010-10-25 07:06:36 +00:00Commented Oct 25, 2010 at 7:06
They are moving datacenters; could be related with that.
