You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@guacamole.apache.org by "Mike Jumper (Jira)" <ji...@apache.org> on 2021/03/07 04:08:00 UTC

[jira] [Reopened] (GUACAMOLE-1298) Automatically enforce request size limits independently of reverse proxy

     [ https://issues.apache.org/jira/browse/GUACAMOLE-1298?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Mike Jumper reopened GUACAMOLE-1298:
------------------------------------

Following the upgrade to Jersey 2.x, annotations for the version of Jackson previously used need to be brought up-to-date with the version of Jackson actually used by the webapp. Annotations from the older Jackson will have no effect.

> Automatically enforce request size limits independently of reverse proxy
> ------------------------------------------------------------------------
>
>                 Key: GUACAMOLE-1298
>                 URL: https://issues.apache.org/jira/browse/GUACAMOLE-1298
>             Project: Guacamole
>          Issue Type: Improvement
>          Components: Documentation, guacamole
>            Reporter: Mike Jumper
>            Assignee: Mike Jumper
>            Priority: Major
>             Fix For: 1.4.0
>
>
> Current Guacamole relies on external services to enforce limits on the size of HTTP requests processed, however users may need to remove externally-enforced limits to allow arbitrarily-large files to be uploaded via file transfer (see GUACAMOLE-1060).
> One possible solution would be to explicitly document the REST endpoint that GUACAMOLE-1060 should apply to, but this seems overly burdensome for administrators. It would be far better if Guacamole simply automatically enforced its own limits wherever appropriate.



--
This message was sent by Atlassian Jira
(v8.3.4#803005)