On Tue, 17 Aug 1999, Duncan Booth wrote:
Well, it seems like the proxy is cutting of the value=123 content.
And ZOPE is complaining, that the proxy request doesn't contain the declared data.
Andreas
Close, but it is actually that the proxy is appending \r\n\0 to the data, and Zope is getting confused. Sorry, it's not easy to read wordwrapped python strings that lengthy :(
'value=123\015\012\015\012\000'
A bit more investigation, and what I think is happening is that Zope receives and processes the request, then it finds the extra '\000' on the end of the data and tries to process that as another request. Not surprisingly this fails, (a tuple unpack throws an exception) but all of the side effects from the original request have been committed as though the request had succeeded. Well, this sounds like a bug in the proxy, but one, that could be probably worked around in ZOPE, right?
Andreas -- Andreas Kostyrka | andreas@mtg.co.at phone: +43/1/7070750 | phone: +43/676/4091256 MTG Handelsges.m.b.H. | fax: +43/1/7065299 Raiffeisenstr. 16/9 | 2320 Zwoelfaxing AUSTRIA