<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 3.2//EN">
<HTML>
<HEAD>
<META HTTP-EQUIV="Content-Type" CONTENT="text/html; charset=utf-8">
<META NAME="Generator" CONTENT="MS Exchange Server version 6.5.7651.59">
<TITLE>Re: [Seaside] Making a store in Seaside</TITLE>
</HEAD>
<BODY>
<!-- Converted from text/plain format -->
<P><FONT SIZE=2>Don't you have to set server protocol as a setting on an application?<BR>
<BR>
Cheers!<BR>
<BR>
-Boris<BR>
(Sent from a BlackBerry)<BR>
<BR>
----- Original Message -----<BR>
From: seaside-bounces@lists.squeakfoundation.org <seaside-bounces@lists.squeakfoundation.org><BR>
To: Seaside - general discussion <seaside@lists.squeakfoundation.org><BR>
Sent: Tue Sep 11 23:24:42 2007<BR>
Subject: Re: [Seaside] Making a store in Seaside<BR>
<BR>
> 1. Native handling. I can just say something like: self call:<BR>
> SecuredComponent withCart: myCart. and the new object will be<BR>
> displayed, it just happens that it's displayed over https (this includes<BR>
> a transparent redirect as part of the component).<BR>
<BR>
I would go with this approach. You create a decoration and in<BR>
#updateRoot: you change the URL from http to https. Whenever you need<BR>
security you add this decoration, whenever you don't you remove it.<BR>
This assumes that you have an identical Apache setup for http and<BR>
https, but that shouldn't be a problem.<BR>
<BR>
Lukas<BR>
<BR>
--<BR>
Lukas Renggli<BR>
<A HREF="http://www.lukas-renggli.ch">http://www.lukas-renggli.ch</A><BR>
_______________________________________________<BR>
Seaside mailing list<BR>
Seaside@lists.squeakfoundation.org<BR>
<A HREF="http://lists.squeakfoundation.org/cgi-bin/mailman/listinfo/seaside">http://lists.squeakfoundation.org/cgi-bin/mailman/listinfo/seaside</A><BR>
</FONT>
</P>
</BODY>
</HTML>