I'm developing an app that needs to see a session cookie to serve up an mp3. It doesn't work so I did some network sniffing to see what's going on. It seems that Safari begins the download and sends the cookie correctly but then it kills that download and kicks off Quicktime which starts a new download without sending the cookie.
Can anyone confirm this behavior? I'm going to work around this by sending the session in the query string, but this feels like a bug to me, Safari should hand its cookies to Quicktime. This isn't a problem in desktop Safari because Quicktime runs as a plugin inside the browser and uses the browser's networking to do its downloading. Is there somewhere for developers to report this kind of bug? --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "iPhoneWebDev" group. To post to this group, send email to [email protected] To unsubscribe from this group, send email to [EMAIL PROTECTED] For more options, visit this group at http://groups.google.com/group/iphonewebdev?hl=en -~----------~----~----~----~------~----~------~--~---
