Timeline for Authorized requests: auth parameter seems broken
Current License: CC BY-SA 2.5
17 events
| when toggle format | what | by | license | comment | |
|---|---|---|---|---|---|
| Mar 8, 2011 at 7:50 | vote | accept | systempuntoout | ||
| Mar 7, 2011 at 18:35 | comment | added | Isaac | @Kevin @systempuntoout: It just occurred to me that despite the number of timeouts I'm seeing on API calls to specific SE sites, I don't think I've ever seen a StackAuth API call timeout. I have no idea if this means anything, though. | |
| Mar 7, 2011 at 7:47 | comment | added | systempuntoout | @Isaac @Kevin still getting timeout; I don't even bother to ask for support to Google App Engine because I already done this in the past on the same topic without any help. (Although in that specific episode, the problem was in the SE side) | |
| Mar 6, 2011 at 23:26 | comment | added | Isaac | @Kevin: From the earlier discussion in the comments, I'd think it's on Google's end, too; I was just not entirely sure that what I was seeing with se-flair matched up to what you and @systempuntoout were talking about. Also, it's good to know that the rate-limiting is always a quick cutoff and never a slow-down. | |
| Mar 6, 2011 at 22:22 | comment | added | Kevin Montrose | @Isaac - like I said, I strongly suspect this is a problem on Google's end; but we're going to look into the network aspect of it anyway to be sure. Also, when we rate-limit we cut you off hard (actual error message returned immediately), we don't slow requests down intentionally ever. | |
| Mar 6, 2011 at 22:02 | comment | added | Isaac | I don't know if it's related, but with se-flair (which also runs on GAE), I've been seeing timeouts (URL fetch didn't complete within 5 seconds) on maybe around 10% of API calls, seemingly at random. (I'd been assuming it was either rate-limiting-related or just that API calls sometimes took longer than 5 seconds.) | |
| Mar 6, 2011 at 21:20 | comment | added | systempuntoout | @Kevin I will re-check tomorrow morning; thanks for the support. | |
| Mar 6, 2011 at 21:15 | comment | added | Kevin Montrose | @systempuntoout - looks like a routing problem from GAE -> us. All those entries are wildcards, so I'd guess the problem is on the GAE side (the problem going away with time would support that). This is assuming its all routes, but only on newer sites of course. Worth noting that all API endpoints are served by the same code, same servers, and same load balancers; there's no meaningful distinction between SO and fitness.SE from the API's point of view. | |
| Mar 6, 2011 at 21:01 | comment | added | systempuntoout | @Kevin stackprinter.com/…; try to change the page parameter from 1 to 5; it randomly fails. | |
| Mar 6, 2011 at 20:43 | comment | added | systempuntoout |
@Kevin forgot to say that the auth error is gone; right now GAE calls to your end randomly go in timeout.
|
|
| Mar 6, 2011 at 20:27 | comment | added | systempuntoout |
@Kevin it seems fixed but not for the new routes like fitness or skeptics for example; is it possible?
|
|
| Mar 6, 2011 at 18:44 | comment | added | Kevin Montrose | @systempuntoout - hmm, no repro. However, looking at the build logs the times this started (and stopped) manifesting kind of match. I've tweaked some more caching code, under the assumption that the API is getting out of sync with stackauth w.r.t. auth parameters. | |
| Mar 6, 2011 at 12:08 | comment | added | systempuntoout | @Kevin it's failing on several endpoints..try with stackprinter.com/topvoted without insert any tags and changing different sites. | |
| Mar 5, 2011 at 17:14 | vote | accept | systempuntoout | ||
| Mar 6, 2011 at 13:48 | |||||
| Mar 5, 2011 at 17:11 | comment | added | Kevin Montrose | @systempuntoout - think I knocked it out (bad API cache, probably due to some networking issues earlier this week). Clicking around everything seems to work on StackPrinter. Can you test from your end? | |
| Mar 5, 2011 at 8:28 | comment | added | systempuntoout | @Kevin uhm, it's still not working; I've added a test link to my question | |
| Mar 5, 2011 at 1:47 | history | answered | Kevin Montrose | CC BY-SA 2.5 |