Jonathan wrote:
As an alternative strategy, how about:
i) set up a url just for this problem user
ii) us apache rewrite to redirect to a non-zope cgi script
iii) use the cgi script to 'fix' the xml
iv) do a redirect with the fixed xml to a 'zope' url
Being all Nu Skool about this, I wonder i
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Dieter Maurer wrote:
> Chris Withers wrote at 2006-10-12 08:35 +0100:
>> Peter Bengtsson wrote:
>>> xml_content = open('validxmlfile.xml').read()
>>> http = httplib.HTTP("localhost", 8080)
>>> http.putrequest("POST", "/uploadExpenseXML")
>> That's not
- Original Message -
From: "Jonathan" <[EMAIL PROTECTED]>
To: "Peter Bengtsson" <[EMAIL PROTECTED]>
Cc:
Sent: Thursday, October 12, 2006 1:21 PM
Subject: Re: [Zope] Re: Sending XML straight down to a zope
- Original Message -
From: &qu
- Original Message -
From: "Peter Bengtsson" <[EMAIL PROTECTED]>
To: "Tres Seaver" <[EMAIL PROTECTED]>
Cc:
Sent: Thursday, October 12, 2006 1:09 PM
Subject: Re: [Zope] Re: Sending XML straight down to a zope
Tres Seaver wrote:
-BEGIN PGP SIGNE
Tres Seaver wrote:
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Peter Bengtsson wrote:
I'm trying to send an XML straight into Zope without specifying it as
a parameter and with a Content-Length. It seems that Zope's mapply
function or whatever it's called digests the raw http body and tries
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Peter Bengtsson wrote:
> I'm trying to send an XML straight into Zope without specifying it as
> a parameter and with a Content-Length. It seems that Zope's mapply
> function or whatever it's called digests the raw http body and tries
> to turn it into
