Nope.
I really thought that setting a future expire header might work.
For now, I set
Configure::write('Session.checkAgent', false);
for request to the problematic action. At least I am only lowering
security for that small part of the app.
On Sep 4, 4:41 pm, Martin Westin <martin.westin...@gmail.com> wrote:
> Not really the reason.
> My guess is that it has something to do with the new way of sanboxing
> plugins and/or the new dual Quicktime. So a video file that needs a
> 32bit codec you would have Safari spawning a plugin process for
> Quicktime which would spawn a 32bit process for the specific rendering
> of the video... somewhere in there things might be screwed up.
>
> But Cake (or PHP) looks to be part of the problem. When requesting a
> real file (just dropped into webroot) Charles shows only one request
> for it... possibly some caching thing could cure it... if the browser
> is explicitly allowed to cache the file then the plugin wouldn't need
> to make another request to the server for it. Must try that...
>
> On Sep 4, 5:00 am, "Brendon Kozlowski (Realm)"
>
>
>
> <brendon...@hotmail.com> wrote:
> > When I have seen others with similar session expiry issues when
> > serving media files, they've solved the problem with setting security
> > to low. Although it's not necessarily a proper solution, perhaps it
> > might lead to a better solution. Have you been able to track down the
> > reason why there are multiple requests/loads on the same file?
>
> > On Sep 3, 1:42 pm, Martin Westin <martin.westin...@gmail.com> wrote:
>
> > > Just noticed that I forgot the mention that this appears to be a Snow
> > > Leopard problem.
> > > Mac OS X 10.6, the new sand-boxed plugins in Safari and the rewritten
> > > Quicktime.
>
> > > On Sep 3, 6:18 pm, Martin Westin <martin.westin...@gmail.com> wrote:
>
> > > > Hi,
> > > > I was wondering if anyone had a good way they use to serve video that
> > > > works for Quicktime inside Safari on a Mac?
>
> > > > Sound simple, right? Just use Media view.
> > > > Problem is that after much checking Charles (debug proxy) clued me in
> > > > on the fact that when you serve the file, the browser first loads it,
> > > > then the plugin loads it aswell. This is a second request with a
> > > > different user agent and you probably know how Cake treat that kind of
> > > > request. Session expires, user logged out and so on.
>
> > > > The only way past it I have found so far is to drop agent checking but
> > > > I am hoping there is a better way. Any ideas?
>
> > > > /Martin- Hide quoted text -
>
> > > - Show quoted text -
--~--~---------~--~----~------------~-------~--~----~
You received this message because you are subscribed to the Google Groups
"CakePHP" group.
To post to this group, send email to cake-php@googlegroups.com
To unsubscribe from this group, send email to
cake-php+unsubscr...@googlegroups.com
For more options, visit this group at
http://groups.google.com/group/cake-php?hl=en
-~----------~----~----~----~------~----~------~--~---
