<html><head><meta http-equiv="Content-Type" content="text/html charset=us-ascii"></head><body style="word-wrap: break-word; -webkit-nbsp-mode: space; -webkit-line-break: after-white-space; "><div>Sam, </div><div><br></div><div>Does the FxOS login UI handle 429s from /account/login? If not, it should probably soon.</div><div><br></div><div>-chris</div><div><br></div><br><div><div>On Apr 1, 2014, at 10:09 AM, Chris Karlof <<a href="mailto:ckarlof@mozilla.com">ckarlof@mozilla.com</a>> wrote:</div><br class="Apple-interchange-newline"><blockquote type="cite"><meta http-equiv="Content-Type" content="text/html charset=us-ascii"><div style="word-wrap: break-word; -webkit-nbsp-mode: space; -webkit-line-break: after-white-space; "><br><div><div>On Apr 1, 2014, at 3:10 AM, Shane Tomlinson <<a href="mailto:stomlinson@mozilla.com">stomlinson@mozilla.com</a>> wrote:</div><br class="Apple-interchange-newline"><blockquote type="cite">Hey all!<br><br>The addition of email rate limiting to the auth-server is causing content-server test failures - since rate limiting wasn't a thing when we wrote our tests, we did not take it into consideration. Can we receive a quick heads up whenever major changes like this are merged so that we can adjust accordingly?<br><br></blockquote><div><br></div><div>This is my responsibility and I dropped the ball. I'll do better in the future.</div><div><br></div><div>And now is a good as a time as any: Nick, we're deploying auth server changes this week that will start returning 429s when a client has made too many requests (e.g., to many bad logins). Your message here <a href="https://github.com/mozilla/fxa-auth-server/issues/394#issuecomment-38246276">https://github.com/mozilla/fxa-auth-server/issues/394#issuecomment-38246276</a> suggests this will be ok, but I'd like to check in again.</div><div><br></div><blockquote type="cite">As an aside, should we tie our tests to a specific git sha of the auth-server? The advantage is we work from a known good sha. Disadvantages include we would potentially be testing against old auth-server code, and we would only see auth-server changes after manual intervention.<br></blockquote><div><br></div><div>I think this is reasonable. We already have a similar process with the fxa-js-client. I would recommend tying it to a release version rather than a git sha, like we do in the js-client.</div><div><br></div><div>-chris</div><div><br></div><div><br></div><div><br></div><br><blockquote type="cite">Thanks,<br>Shane<br>_______________________________________________<br>Dev-fxacct mailing list<br><a href="mailto:Dev-fxacct@mozilla.org">Dev-fxacct@mozilla.org</a><br><a href="https://mail.mozilla.org/listinfo/dev-fxacct">https://mail.mozilla.org/listinfo/dev-fxacct</a><br></blockquote></div><br></div>_______________________________________________<br>Dev-fxacct mailing list<br><a href="mailto:Dev-fxacct@mozilla.org">Dev-fxacct@mozilla.org</a><br>https://mail.mozilla.org/listinfo/dev-fxacct<br></blockquote></div><br></body></html>