title: hoodie app on nodejitsu: added %2f confounding couchdb request
body: <p>I have deployed a basic tutorial hoodie app on nodejitsu (which works fine on my local server).  Here is the url of my deployed app:</p>
  
  <p><a href="http://reggie.nodejitsu.com" rel="nofollow">http://reggie.nodejitsu.com</a></p>
  
  <p>A signup button is supposed to appear in the upper right hand corner after user login status is confirmed, which it does, but after a very, very long time.</p>
  
  <p>Looking at the log file on nodejitsu, I see (personal detail redacted):</p>
  
  <pre><code>Streaming logging information
  
  out Thu, 13 Nov 2014 18:51:25 GMT Starting Plugin: 'hoodie-plugin-users'
  out Thu, 13 Nov 2014 18:51:25 GMT All plugins started.
  err Thu, 13 Nov 2014 18:51:25 GMT { [Error: not_found
  missing]
  </code></pre>
  
  <p>and then a little later:</p>
  
  <pre><code>_header: 'GET /_users/org.couchdb.user%3Aadmin%2F HTTP/1.1\r\nHost: xxxxxxxxx.iriscouch.com\r\nAccept: application/json\r\nAuthorization: Basic YWRtaW46bm9uY3JpdGljYWw=\r\nConnection: keep-alive\r\n\r\n',
  </code></pre>
  
  <p>and then a little later:</p>
  
  <pre><code>out Thu, 13 Nov 2014 18:51:25 GMT 
  err Thu, 13 Nov 2014 18:51:25 GMT Error confirming user: Error: not_found
  missing
  </code></pre>
  
  <p>If I request the endpoint <code>/_users/org.couchdb.user%3Aadmin%2F</code> from my nodejitsu couchdb instance directly, that fails with <code>{"error":"not_found","reason":"missing"}</code>. But if I remove the trailing encoded slash, <code>/_users/org.couchdb.user%3Aadmin</code>, I get the user returned as expected.  </p>
  
  <p>So it seems to me the trailing encoded slash (<code>%2f</code>) is messing up the authentication with couchdb, and then I presume the very long delay the app takes to figure out if the user is logged in to the app is resulting from a timeout trying access the database without the required credentials.  But I do not know how to stop the trailing encoded slash from being added.</p>
  
  <p>Have I diagnosed the issue correctly, and either way, how can I resolve this issue?</p>
  
  <p>Thanks!</p>