« Return to Thread: HTTP PUT strange behavior

Re: HTTP PUT strange behavior

by Michael Haubenwallner-2 :: Rate this Message:

Reply to Author | View in Thread

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

Adrian Tofan wrote:
> I have read a related problem on the zope forums which they solved by
> changing the web server from paster to zserver. I don't understand this part
> and I don't know how to do it (if posible in grok).
>

I found this in http://pypi.python.org/pypi/zope.publisher

3.5.3 (2008-06-20)

Bugs fixed:

    * It turns out that some Web servers (Paste for example) do not send
the EOF character after the data has been transmitted and the read() of
the cached stream simply hangs if no expected content length has been
specified.

Could be this is a fix to the problem you described.
Grok itself uses zope.publisher 3.4.6 atm.

You could try and patch the z.p 3.4.6 egg along the bugix from 3.5.3 and
  see if that works for you.

Hth,
Michael

- --
http://blog.d2m.at
http://planetzope.org

-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.6 (GNU/Linux)
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org

iD8DBQFKHlpnl0uAvQJUKVYRAsIfAJ9tIv74IMyaPk91hNeY2jYQMpitbQCfSX/f
GwYJVlM8TvWSGpTu/W37mKw=
=8OT0
-----END PGP SIGNATURE-----

_______________________________________________
Grok-dev mailing list
Grok-dev@...
http://mail.zope.org/mailman/listinfo/grok-dev

 « Return to Thread: HTTP PUT strange behavior