[Seaside] Safari on Leopard Apache post problem

Boris Popov boris at deepcovelabs.com
Wed Nov 14 00:22:58 UTC 2007

That's pretty much the same configuration I'm using and we haven't seen
this problem yet. Could you perhaps post your Apache config so we could


DeepCove Labs Ltd.
4th floor 595 Howe Street
Vancouver, Canada V6C 2T5

boris at deepcovelabs.com


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

Thank you.

> -----Original Message-----
> From: seaside-bounces at lists.squeakfoundation.org [mailto:seaside-
> bounces at lists.squeakfoundation.org] On Behalf Of Roger Whitney
> Sent: Tuesday, November 13, 2007 4:20 PM
> To: Seaside - general discussion
> Subject: [Seaside] Safari on Leopard Apache post problem
> I have a problem with the new Safari on Leopard (Mac OS 10.5)
> accessing a Seaside application running behind Apache and hope someone
> can shed some light on it.
> I am using Seaside 2.8 on VW 7.5. When I run Seaside as a standalone
> web server in VW (the tiny Web server in VW) Safari in Leopard has no
> problems accessing the Seaside application. When I run the Seaside
> application behind Apache there is no problem with Firefox, Opera and
> older versions of Safari accessing the application.
> When I use Safari 3.0.4, which comes on Leopard, there are problems
> with posts from a seaside page. The problem occurs not only on my code
> but in Functional Seaside Test Suite examples. When I click on a
> button to submit a form the bowser says it is contacting the server
> and seems to wait for ever without timing out. On the server side I
> first get the POST request. According to the log file 15 seconds later
> I get a GET request. The server and client are running on the same
> machine (Dual Core), so there is no network delay. A few seconds later
> a second GET request comes from Safari. If I stop the request from
> Safari and then have it reload the page I do get the reply to the
> Since Safari 3.0.4 does work when talking directly to the VW web
> server there is some problem with Safari 3.0.4 and Apache. Does anyone
> have any idea how to configure Apache to avoid this? Unfortunately
> some of my users can only access port 80, so I have to run behind
> Apache.
> ----
> Roger Whitney              Department of Computer Science
> whitney at cs.sdsu.edu        San Diego State University
> http://www.eli.sdsu.edu/   San Diego, CA 92182-7720
> _______________________________________________
> seaside mailing list
> seaside at lists.squeakfoundation.org
> http://lists.squeakfoundation.org/cgi-bin/mailman/listinfo/seaside

More information about the seaside mailing list