Github user olafura commented on the pull request:

    https://github.com/apache/couchdb/pull/284#issuecomment-64914833
  
    Sound reasonable, if I remember right looking over the code, they have a 
fix for this incorrect behavior not the other way round. It takes a lot of code 
to check if it's alright to send people on their way instead of things just 
working. I think I something like that when I first encountered the bug. There 
are also so many cookie timeout things that just work when this behavior is 
right. Dealing with a 302 is very easy, just pipe the location to 
window.location. 
    
http://stackoverflow.com/questions/6955308/in-an-ajax-call-302-is-not-followed


---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not have this feature
enabled and wishes so, or if the feature is enabled but not working, please
contact infrastructure at infrastruct...@apache.org or file a JIRA ticket
with INFRA.
---

Reply via email to