[Seaside] Working with CSS designers

Boris Popov boris at deepcovelabs.com
Mon May 7 20:16:20 UTC 2007

When deploying, the application gets configured with a resource URL
pointing to S3,

 preferenceAt: #resourceBaseUrl
 put: 'https://s3.amazonaws.com/bucketname/' , self version

The browser won't show a warning because resources are secure and
browser trusts the CA, you'd only get a warning if you were serving
non-secure resources from a secure page (note the https in the URL),



DeepCove Labs Ltd.
4th floor 595 Howe Street
Vancouver, Canada V6C 2T5

boris at deepcovelabs.com


This email is intended only for the persons named in the message
header. Unless otherwise indicated, it contains information that is
private and confidential. If you have received it in error, please
notify the sender and delete the entire message including any

Thank you.

> -----Original Message-----
> From: seaside-bounces at lists.squeakfoundation.org [mailto:seaside-
> bounces at lists.squeakfoundation.org] On Behalf Of Thierry Thelliez
> Sent: Monday, May 07, 2007 1:11 PM
> To: Seaside - general discussion
> Subject: Re: [Seaside] Working with CSS designers
> Boris,
> About S3, how does that work for the domain name and URL? If your
> application is http://www.myapp.com/ , how do you serve the
> images/css/js from the same domain?
> Or do you just point to Amazon (I assume that this is an Amazon domain
> name)? But then, in an https environment, doesn't that trigger a
> warning on the browser side?
> Thanks,
> Thierry
> _______________________________________________
> Seaside mailing list
> Seaside at lists.squeakfoundation.org
> http://lists.squeakfoundation.org/cgi-bin/mailman/listinfo/seaside

More information about the seaside mailing list