Hi:

If a user logs in using an HTTPS secured page, then anything that is in the journal summary that is streamed from amazon s3 is giving the user a security warning.  This is because the template (or maybe the entire app) isn't smart enough to use https to stream from amazon when on a secured page.  Is there any way around this issue or will I have to skip using S3 altogether? 

Any help appreciated.

Thanks.

-eLindy