Actually, the t:formdata is always an object stream that has been GZiped and
mime-encoded.
The GZip support added in 5.1 concerns entire requests: for pages, for
assets.
On Thu, Sep 24, 2009 at 12:44 PM, Ovidiu Hurducas wrote:
> Thanks! ... it was a wrong t:formdata value. Another thing: it is w
Thanks! ... it was a wrong t:formdata value. Another thing: it is working
with and without GZIP-ing the request. Tapestry seems to handle both
situations.
On Thu, Sep 24, 2009 at 10:36 AM, Kalle Korhonen wrote:
> And obviously you need to gzip the request.
>
> On Thu, Sep 24, 2009 at 12:32 AM,
And obviously you need to gzip the request.
On Thu, Sep 24, 2009 at 12:32 AM, Kalle Korhonen
wrote:
> From the page source, check what the value of hidden field t:formdata
> is and send it together with the rest of your multipart form data and
> it'll work. The value of t:formdata changes only if
>From the page source, check what the value of hidden field t:formdata
is and send it together with the rest of your multipart form data and
it'll work. The value of t:formdata changes only if you change the
form itself (add/remove fields).
Kalle
On Wed, Sep 23, 2009 at 4:02 PM, Ovidiu Hurducas
I've recently migrated an Tapestry 5.0.18 application to Tapestry version
5.1.0.5.
I have this form that isn't working anymore
http://tapestry.apache.org/schema/tapestry_5_0_0.xsd";>
I'm using Apache HttpClient 3.1 to POST a multipart form (file upload).
And the stack