title: Asynchronous methods, callback URIs, and local development
body: <p>I'm working with the Pocket (Formerly Read It Later) API, which requires some asynchronous methods - something I'm new to. </p>
  
  <p>I understand the <em>very</em> basic principle that asynchronous methods improve performance by allowing the application to move forward while processing more taxing methods. </p>
  
  <p>With the API, I have to use an async method to authenticate the user. When calling one of the methods, I must provide a call-back uri. This tells Pocket what site they should reroute to after authentication. I see that the uri is correct in the authentication page's url:</p>
  
  <pre><code>https://getpocket.com/auth/authorize?request_token=5dfc83ba-1116-3c4c-
  bbbfb2&amp;redirect_uri=http://localhost:44320/index.aspx
  </code></pre>
  
  <p>For some reason, however, this just prompts Pocket's Authentication page to reload. When trying a "dummy" uri, like <a href="http://www.google.com" rel="nofollow">http://www.google.com</a>, the page correctly redirects. This tells me there's something it doesn't like about "localhost". </p>
  
  <p>Are there any tips for avoiding this?</p>