Different credentials should indeed result in completely different response. My advice, as always, is to try your requests with curl and see if the failure case is still present. Some developers have run into weird cases with the NS* HTTP client libraries.
On Sun, Nov 16, 2008 at 11:49, Nick Toumpelis <[EMAIL PROTECTED]> wrote: > I'm using the default protocol cache policy for HTTPS, which I presume to be > the same as HTTP. For the latter, NSURLRequest refreshes the data > appropriately: > http://developer.apple.com/documentation/Cocoa/Conceptual/URLLoadingSystem/Concepts/CachePolicies.html > I assumed that different authentication credentials meant that the previous > (cached) request would not be used (but I could be wrong). > > > On 16 Νοε 2008, at 9:27 ΜΜ, Alex Payne wrote: > > Are you calling these methods in your browser? Could your browser be > showing you cached responses? > > On Sun, Nov 16, 2008 at 10:45, Nicholas Toumpelis > <[EMAIL PROTECTED]> wrote: > > Dear Alex, > > I had a problem recently, namely that the Favorites and User timelines > > do not update correctly when switching between users. > > In particular, after changing the user credentials, both timelines > > seem stuck to the previous authenticated user. The calls I was using > > are these: http://username:[EMAIL PROTECTED]/favorites.xml and > > statuses/user_timeline.xml. Other timelines do not have this problem. > > On the other hand, when I use the > http://username:[EMAIL PROTECTED]/favorites/bob.xml > > and http://username:[EMAIL PROTECTED]/statuses/user_timeline/bob.xml > > calls, the updates appear as expected. > > Thanks, > > Nick > > > Nick Toumpelis > > email: [EMAIL PROTECTED] > > twitter: macsphere > > GTalk: nicktoumpelis > > > > > > > -- > Alex Payne - API Lead, Twitter, Inc. > http://twitter.com/al3x > > Nick Toumpelis > email: [EMAIL PROTECTED] > twitter: macsphere > GTalk: nicktoumpelis > > > > > > > > -- Alex Payne - API Lead, Twitter, Inc. http://twitter.com/al3x
