[Seaside] Seaside 2.8 and Apache

Boris Popov boris at deepcovelabs.com
Wed Nov 14 16:33:27 UTC 2007


Did you revert the changes you did on Apache side, as you said you had
to change it from http://localhost:9090/seaside/fred to "https" and
that's not right? Then try it again and let us know.

-Boris

-- 
+1.604.689.0322
DeepCove Labs Ltd.
4th floor 595 Howe Street
Vancouver, Canada V6C 2T5
http://tinyurl.com/r7uw4

boris at deepcovelabs.com

CONFIDENTIALITY NOTICE

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
attachments.

Thank you.

> -----Original Message-----
> From: seaside-bounces at lists.squeakfoundation.org [mailto:seaside-
> bounces at lists.squeakfoundation.org] On Behalf Of Richard Eng
> Sent: Wednesday, November 14, 2007 8:31 AM
> To: Seaside - general discussion
> Subject: Re: [Seaside] Seaside 2.8 and Apache
> 
> Yes, but I still don't know what to do to work around this problem.
> Seaside
> 2.7 didn't have this problem. Setting serverPort and serverProtocol is
> causing an Internal Server Error. So what else do I need to do?
> 
> Thanks,
> Richard
> 
> --------
> Oh no no, seaside itself doesn't do ssl, apache does. You just proxy
non-
> ssl
> app, but it needs to know what URLs to present to the outside world.
> 
> Cheers!
> 
> -Boris
> (Sent from a BlackBerry)
> 
> ----- Original Message -----
> From: seaside-bounces at lists.squeakfoundation.org <seaside-bounces
at
> lists.squeakfoundation.org>
> To: Seaside Mailinglist <seaside at lists.squeakfoundation.org>
> Sent: Wed Nov 14 05:12:18 2007
> Subject: Re: [Seaside] Seaside 2.8 and Apache
> 
> Interesting. Why wasn't this needed in Seaside 2.7 ?
> 
> At any rate, it doesn't work. I get "500 Internal Server Error".
> 
> In Seaside config, I set Server Port and Server Protocol. I found I
also
> had
> to modify the httpd.conf so that
> 
> http://localhost:9090/seaside/fred
> 
> becomes
> 
> https://localhost:9090/seaside/fred
> 
> But then I got Internal Server Error. So I went back to Seaside config
and
> set
> 
> Resource Base Url -> /var/www/ssl
> Server Hostname -> www.goodsexnetwork.com
> Server Path -> /home/richard/seaside (yes, this is where my Seaside
image
> resides)
> 
> I have no idea whether these are the expected settings.
> 
> Anyway, it didn't fix the problem. I still have Internal Server Error.
> 
> Regards,
> Richard
> 
> --------------
> And #serverPort to 443.
> 
> Cheers
> 
> Liliana
> 
> 
> 
> From: Boris Popov [mailto:boris at deepcovelabs.com]
> Sent: 14 November 2007 09:02 AM
> To: seaside at lists.squeakfoundation.org
> Subject: Re: [Seaside] Seaside 2.8 and Apache2
> 
> 
> 
> Seaside needs to know that its hosted behind ssl, did you set the
> #serverProtocol to be #https?
> 
> Cheers!
> 
> -Boris
> (Sent from a BlackBerry)
> 
> 
> _______________________________________________
> seaside mailing list
> seaside at lists.squeakfoundation.org
> http://lists.squeakfoundation.org/cgi-bin/mailman/listinfo/seaside


More information about the seaside mailing list