[
https://issues.apache.org/jira/browse/WICKET-1861?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12671894#action_12671894
]
Matej Knopp commented on WICKET-1861:
-------------------------------------
Can't we omit the check if no maxSize is set?
> Inevitable UnknownSizeException with HTTPS
> ------------------------------------------
>
> Key: WICKET-1861
> URL: https://issues.apache.org/jira/browse/WICKET-1861
> Project: Wicket
> Issue Type: Bug
> Components: wicket
> Affects Versions: 1.4-M3
> Environment: Caucho Resin 3.2 behind apache2
> Reporter: uwe schaefer
> Assignee: Juergen Donnerstag
> Fix For: 1.4-RC2
>
>
> When using a FileUploadField in a HTTPS environment, the request always
> returns a request-size of -1.
> In that case, FileUploadBase rejects to process the reuqest, no matter what
> (or if) a maxSize is defined:
> 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");
> }
> this makes it impossible to use fileUploads with HTTPS in this environment at
> all.
> I think, this _sanity check_ should not be done if either HTTPS is used, or
> the developer does not care (expressed by not setting any maxSize).
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
