You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@cocoon.apache.org by bu...@apache.org on 2005/04/07 11:55:02 UTC

DO NOT REPLY [Bug 34344] New: - Cforms upload widget weight limitation validator

DO NOT REPLY TO THIS EMAIL, BUT PLEASE POST YOUR BUG�
RELATED COMMENTS THROUGH THE WEB INTERFACE AVAILABLE AT
<http://issues.apache.org/bugzilla/show_bug.cgi?id=34344>.
ANY REPLY MADE TO THIS MESSAGE WILL NOT BE COLLECTED AND�
INSERTED IN THE BUG DATABASE.

http://issues.apache.org/bugzilla/show_bug.cgi?id=34344

           Summary: Cforms upload widget weight limitation validator
           Product: Cocoon 2
           Version: 2.1.6
          Platform: Other
        OS/Version: other
            Status: NEW
          Severity: normal
          Priority: P2
         Component: CocoonForms
        AssignedTo: dev@cocoon.apache.org
        ReportedBy: t.katelbach@systheo.com


>My Form contains upload widgets, 
>I have limited the size parameter in web.xml upload config.
>But I would like to get the oversized error as a form validation error.
>In the Form validation docs, it says upload widget supports validation but
>no idea of which rules.
Sylvain Wallez wrote:
There are no built-in validators for the upload widget except the 
mime-type checks. You can however plug an custom validator to check e.g. 
the content of the uploaded file.

However, your problem is different and cannot be handled with the 
current CForms, and worse, with the current Cocoon as oversized upload 
is filtered very early in the request processing, i.e. in the CocoonServlet.

What that means is that the upload widget has no means to know that 
upload has occured but was rejected. We need for this to enhance the 
multipart handling to pass an indication of the rejected upload to the 
application. Note that such indication would be useful also to detect 
that upload isn't enabled in web.xml.

-- 
Configure bugmail: http://issues.apache.org/bugzilla/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the assignee for the bug, or are watching the assignee.