[Seaside] Seaside and Apache

[Bill Schwab]

Philippe,

IE - what's that? :)  Firefox 3 presents a slightly "alarmist" view of a
self-signed cert, but I disagree that it prevents their use.  In the
end, it obediently creates an "exception," temporary or permanent, to
recognize the certificate.  Since I frequently develop and test on
isolated machines, I will be using them for a long time.

That said, we are investigating getting away from machine-specific
certificates and blowing for one that covers our entire domain.  If that
happens, I will not need to self-sign on publicly visble machines.

What are your thoughts on the configuration file I posted?  Am I making
sense with the locations?  Do I need any specific ordering (most
specific first), etc.?

Bill




====================
Philippe Marschall philippe.marschall at gmail.com 
> After a few days of getting almost nothing (even in logs, which was
> driving me nuts), I tried a different approach and had a self-signed
> https Apache proxying Seaside.

Beware of self-signed certificates. Firefox 3 and IE 7 go to great
lengths preventing you to use them.

Cheers
Philippe

Wilhelm K. Schwab, Ph.D.
University of Florida
Department of Anesthesiology
PO Box 100254
Gainesville, FL 32610-0254

Email: bschwab at anest.ufl.edu
Tel: (352) 273-6785
FAX: (352) 392-7029