Re: HTTPS and FileUpload
Igor Vaynberg schrieb: hmm, create a jira issue. mabe if you override getmaxsize on the form and return -1 or null -indicating you dont care, we should not error out done. https://issues.apache.org/jira/browse/WICKET-1861 thx uwe - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
HTTPS and FileUpload
hi i think i hit a bug within wicket (or maybe it is a bug within the appserver?). i have a FileUpload on a wicket form and everything is smooth, _until_ it is taken to https. it looks like in https, the request does not (at least in caucho resin) tell the size of the request. This means (whatever maxSize is defined) wicket rejects to process it: org.apache.wicket.util.upload.FileUploadBase:236 (wicket 1.4m3) if (requestSize == -1) { throw new UnknownSizeException( the request was rejected because its size is unknown); } is there a way around, or does this sanity check break on https? cu uwe ps: shall i open an isue for that? i just commented those lines out locally and it works nicely with http as well as http. - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: HTTPS and FileUpload
hmm, create a jira issue. mabe if you override getmaxsize on the form and return -1 or null -indicating you dont care, we should not error out -igor On Mon, Oct 6, 2008 at 4:10 AM, Uwe Schäfer [EMAIL PROTECTED] wrote: hi i think i hit a bug within wicket (or maybe it is a bug within the appserver?). i have a FileUpload on a wicket form and everything is smooth, _until_ it is taken to https. it looks like in https, the request does not (at least in caucho resin) tell the size of the request. This means (whatever maxSize is defined) wicket rejects to process it: org.apache.wicket.util.upload.FileUploadBase:236 (wicket 1.4m3) if (requestSize == -1) { throw new UnknownSizeException( the request was rejected because its size is unknown); } is there a way around, or does this sanity check break on https? cu uwe ps: shall i open an isue for that? i just commented those lines out locally and it works nicely with http as well as http. - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]