[Seaside] Seaside 2.8 and Apache

[Richard Eng]

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)