[Swazoo/Seaside] Unicode encoding & HTTPS/OpenSLL support

Hi Dolphin guru,
   
   I'm using Sport/Swazoo/Seaside port by Esteban A. Maringolo for a
while with much delight, thanks indeed, but had some fuss disturbing
me off and on, cann't figure how to solve it by myself.

   First of all, it seemed that the web page rendered by Seaside,
cann't display the correct encoding as specified at the html head tag,
i.e. the web browser always use the UTF-8 encoding instead of the
charset = 'big5' statement on the rendered page, why?

   Second, it seemed that  there is no official support of
HTTPS/OpenSLL library under current Swazoo/Seaside framework. which is
in great want in view of current active e-commerce services , usually
as default and available in popular web servers.

    Should Swazoo commuity on VW/Squeak/Dolphin dialects consider to
add these functionalities,  an add-on wrapping of OpenSLL ( OA do it ?
) and enhancement on Swazoo supported protocols for HTTPs ?

Best regards,

Tk Kuo

Hi Tk,

> Should Swazoo commuity on VW/Squeak/Dolphin dialects consider to
> add these functionalities,  an add-on wrapping of OpenSLL ( OA do it ?
> ) and enhancement on Swazoo supported protocols for HTTPs ?

I agree that Swazoo support for https would be handy ... FWIW: I recall
a VW version of Swazoo that supported https, although I believe it was
based on VW's native SSL implementation.

I work around this missing functionality in Dolphin by running Swazoo
as an internal server and using IIS (or you could use Apache) as my
public web server. IIS (or Apache) handle the https requests and proxy
them through to Swazoo as normal http requests.

Even if Dolphin Swazoo had https support, I would continue to use IIS
as my public server as there are a number of other benefits such as
serving static content through IIS and using IIS authentication.

I think mod proxy will do this for Apache, although I have not tried.
For IIS, I use ISAPIRewrite from: http://www.helicontech.com/

Steve
 --
[hidden email]