Re: 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
[hidden email]
http://lists.squeakfoundation.org/cgi-bin/mailman/listinfo/seaside

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: [hidden email] <[hidden email]>
To: Seaside Mailinglist <[hidden email]>
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 [[hidden email] 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
[hidden email]
http://lists.squeakfoundation.org/cgi-bin/mailman/listinfo/seaside

_______________________________________________
seaside mailing list
[hidden email]
http://lists.squeakfoundation.org/cgi-bin/mailman/listinfo/seaside

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
[hidden email]
http://lists.squeakfoundation.org/cgi-bin/mailman/listinfo/seaside

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

[hidden email]

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.
non- at also 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 _______________________________________________
seaside mailing list
[hidden email]
http://lists.squeakfoundation.org/cgi-bin/mailman/listinfo/seaside

From,

http://leftshore.files.wordpress.com/2006/10/apacheandseaside.txt

SSLEngine On
SSLCertificateFile /usr/local/share/apache2/ssl/www.mydomain.com.crt
SSLCertificateKeyFile /usr/local/share/apache2/ssl/www.mydomain.com.key
SetEnvIf User-Agent ".*MSIE.*" nokeepalive ssl-unclean-shutdown
ProxyRequests Off
ProxyPreserveHost On
<Proxy *>
 Order deny,allow
 Allow from none
</Proxy>
<Location /online>
 Order deny,allow
 Allow from all
 ProxyPass http://localhost:8008/online
 ProxyPassReverse http://localhost:8008/online
</Location>

Then in Smalltalk,

MyRootComponent>>install
 (self registerAsApplication: self applicationName)
   preferenceAt: #deploymentMode put: true;
   preferenceAt: #serverProtocol put: #https;
   preferenceAt: #serverPort put: 443.

-Boris

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

[hidden email]

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: Boris Popov
> Sent: Wednesday, November 14, 2007 8:33 AM
> To: 'Seaside - general discussion'
> Subject: RE: [Seaside] Seaside 2.8 and Apache
>
> 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 is at also config Error. _______________________________________________
seaside mailing list
[hidden email]
http://lists.squeakfoundation.org/cgi-bin/mailman/listinfo/seaside

I managed to get it working with deployment mode, Server Port and Server
Protocol set appropriately, but now it breaks Apache's load balancer.

I think I'll just go back to Seaside 2.7. It's too much trouble trying to
get Seaside 2.8 to work (unless someone has a quick solution to load
balancing).

I should've heeded the old adage:  If it ain't broke, don't fix it. Serves
me right for being ambitious...

I was simply trying to improve performance because I like Seaside 2.8's
faster rendering speed and smaller memory footprint.

Regards,
Richard

-------
From,

http://leftshore.files.wordpress.com/2006/10/apacheandseaside.txt

SSLEngine On
SSLCertificateFile /usr/local/share/apache2/ssl/www.mydomain.com.crt
SSLCertificateKeyFile /usr/local/share/apache2/ssl/www.mydomain.com.key
SetEnvIf User-Agent ".*MSIE.*" nokeepalive ssl-unclean-shutdown
ProxyRequests Off
ProxyPreserveHost On
<Proxy *>
 Order deny,allow
 Allow from none
</Proxy>
<Location /online>
 Order deny,allow
 Allow from all
 ProxyPass http://localhost:8008/online
 ProxyPassReverse http://localhost:8008/online
</Location>

Then in Smalltalk,

MyRootComponent>>install
 (self registerAsApplication: self applicationName)
   preferenceAt: #deploymentMode put: true;
   preferenceAt: #serverProtocol put: #https;
   preferenceAt: #serverPort put: 443.

-Boris

> -----Original Message-----
> From: Boris Popov
> Sent: Wednesday, November 14, 2007 8:33 AM
> To: 'Seaside - general discussion'
> Subject: RE: [Seaside] Seaside 2.8 and Apache
>
> 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


_______________________________________________
seaside mailing list
[hidden email]
http://lists.squeakfoundation.org/cgi-bin/mailman/listinfo/seaside

How does version 2.7 work without setting those things in the first
place? I must be missing something as they aren't new to 2.8 in any way
and would be required if you were fronting http server in Smalltalk with
SSL on either one.

-Boris

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

[hidden email]

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: [hidden email] [mailto:seaside-
> [hidden email]] On Behalf Of Richard Eng
> Sent: Wednesday, November 14, 2007 10:22 AM
> To: Seaside - general discussion
> Subject: Re: [Seaside] Seaside 2.8 and Apache
>
> I managed to get it working with deployment mode, Server Port and
Server
> Protocol set appropriately, but now it breaks Apache's load balancer.
>
> I think I'll just go back to Seaside 2.7. It's too much trouble trying
to
> get Seaside 2.8 to work (unless someone has a quick solution to load
> balancing).
>
> I should've heeded the old adage:  If it ain't broke, don't fix it.
Serves
> me right for being ambitious...
>
> I was simply trying to improve performance because I like Seaside
2.8's /usr/local/share/apache2/ssl/www.mydomain.com.key had _______________________________________________
seaside mailing list
[hidden email]
http://lists.squeakfoundation.org/cgi-bin/mailman/listinfo/seaside

Very good question. Excellent question. Exactly the question I asked in my
first post.

If we can find the answer to that question, then we will understand why
Seaside 2.8 won't work with Apache's load balancer.

Richard

-------
How does version 2.7 work without setting those things in the first
place? I must be missing something as they aren't new to 2.8 in any way
and would be required if you were fronting http server in Smalltalk with
SSL on either one.

-Boris


_______________________________________________
seaside mailing list
[hidden email]
http://lists.squeakfoundation.org/cgi-bin/mailman/listinfo/seaside

That's something only you could investigate. In my set up not setting
those values will result in HTML that includes "http" instead of
"https".

-Boris

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

[hidden email]

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: [hidden email] [mailto:seaside-
> [hidden email]] On Behalf Of Richard Eng
> Sent: Wednesday, November 14, 2007 10:37 AM
> To: Seaside - general discussion
> Subject: Re: [Seaside] Seaside 2.8 and Apache
>
> Very good question. Excellent question. Exactly the question I asked
in my
> first post.
>
> If we can find the answer to that question, then we will understand
why
> Seaside 2.8 won't work with Apache's load balancer.
>
> Richard
>
> -------
> How does version 2.7 work without setting those things in the first
> place? I must be missing something as they aren't new to 2.8 in any
way
> and would be required if you were fronting http server in Smalltalk
with
> SSL on either one.
>
> -Boris
>
>
> _______________________________________________
> seaside mailing list
> [hidden email]
> http://lists.squeakfoundation.org/cgi-bin/mailman/listinfo/seaside
_______________________________________________
seaside mailing list
[hidden email]
http://lists.squeakfoundation.org/cgi-bin/mailman/listinfo/seaside

Good news. I've got it working...

I started from scratch with both Seaside 2.7 and 2.8. Step by step, I
carefully built up the images in parallel.

Then I tested each image with the Apache balancer httpd.conf, switching back
and forth between Seaside 2.7 and 2.8. Finally, when I got everything
carefully constructed, with no unexpected diversions, I was able to
duplicate the original problem.

Then I set the Server Port and Server Protocol for the Seaside 2.8 image
*only*. And now it works!

For whatever reason, I have to be very, very meticulous and careful in
constructing the server environment. Order of operation is important. No
unnecessary diversions should be allowed. As long as I stick to this strict
regimen, I should be able to reliably deploy my web app without surprise.

Of course, I still haven't answered the question why Seaside 2.7 worked
without the correct Server Port and Protocol. But it's not worth my time and
energy to figure it out.

Thanks to everyone.

(I better add this to my blog at http://open-sourcerer.blogspot.com/ )

Regards,
Richard

---------
That's something only you could investigate. In my set up not setting
those values will result in HTML that includes "http" instead of
"https".

-Boris


_______________________________________________
seaside mailing list
[hidden email]
http://lists.squeakfoundation.org/cgi-bin/mailman/listinfo/seaside

Cool!

-Boris

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

[hidden email]

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.
switching
> back
> and forth between Seaside 2.7 and 2.8. Finally, when I got everything
> carefully constructed, with no unexpected diversions, I was able to
> duplicate the original problem.
>
> Then I set the Server Port and Server Protocol for the Seaside 2.8
image
> *only*. And now it works!
>
> For whatever reason, I have to be very, very meticulous and careful in
> constructing the server environment. Order of operation is important.
No
> unnecessary diversions should be allowed. As long as I stick to this
> strict
> regimen, I should be able to reliably deploy my web app without
surprise.
>
> Of course, I still haven't answered the question why Seaside 2.7
worked
> without the correct Server Port and Protocol. But it's not worth my
time _______________________________________________
seaside mailing list
[hidden email]
http://lists.squeakfoundation.org/cgi-bin/mailman/listinfo/seaside