Notifications

514 views

Description

Forms can not be saved or submitted when large strings are present, for too large network response, but with no warning messages for the form user. The Save/Submit operation hangs and times out, eventually leading the user to an unexpected page, with the form not retaining edits.

Example localhost log for KB Article TinyMCE limitation when trying to save/update:

http-20 New transaction BFA2066213EE2200ED373D62F244B099 #42137 /kb_knowledge.do
Default-thread-16 BFA2066213EE2200ED373D62F244B099 #42137 /kb_knowledge.do Parameters -------------------------
Default-thread-16 BFA2066213EE2200ED373D62F244B099 *** Start #42,137, path: /kb_knowledge.do, user: shahid.shah@snc
Default-thread-16 BFA2066213EE2200ED373D62F244B099 WARNING *** WARNING *** WithTag2 called with no query, returning a new record instead
Default-thread-16 BFA2066213EE2200ED373D62F244B099 *** End #42,137, path: /kb_knowledge.do, user: shahid.shah@snc, total transaction time: 0:00:00.170, transaction processing time: 0:00:00.170, network: 0:00:00.004, chars: 46,476, uncompressed chars: 198,639, SQL time: 17 (count: 32), business rule: 1 (count: 1), phase 1 form length: 632,460, largest chunk written: 46,476, request parms size: 40, largest input read: 0
Default-thread-16 BFA2066213EE2200ED373D62F244B099 #42137 /kb_knowledge.do -- total transaction time: 0:00:00.170, transaction processing time: 0:00:00.170, total wait time: 0:00:00.000, session wait: 0:00:00.000, semaphore wait: 0:00:00.000, source: 10.255.28.171, chars: 46,476, uncompressed chars: 198,639, SQL time: 17 (count: 33), business rule: 1 (count: 1), phase 1 form length: 632,460, largest chunk written: 46,476, request parms size: 40, largest input read: 0

Steps to Reproduce

 

When adding content larger than 2 MB into a form, the error can occur.

Apache Tomcat by default sets a limit on the maximum size of HTTP POST requests it accepts. In Tomcat 5, this limit is set to 2 MB.

 

Workaround

The default limit set to the system property is by design and considered secure, content larger than 2MB can not be inserted into a form. The workaround is to attach files to the form instead, the attachment maximum size allowed is set by the Maximum file attachment size in megabytes property (com.glide.attachment.max_size).

 


Related Problem: PRB718833

Seen In

Berlin Hot Fix 5
Calgary Patch 7 Hot Fix 4
Dublin EA 1
Geneva Patch 4
Geneva Patch 6 Hot Fix 2
Helsinki Patch 1
Helsinki Patch 5
SR - IRM - Audit Management - New York 2019 Q3
SR - IRM - GRC Profiles - Madrid 2019 Q2
SR - IRM - GRC Workbench - New York 2019 Q3
SR - IRM - PA Premium Integration - New York 2019 Q3
SR - IRM - Policy and Compliance - Madrid 2019 Q2
SR - IRM - Risk Management - New York 2019 Q3
SR - IRM - SIG Assessment Legacy - Madrid 2019 Q1
SR - IRM - Vendor Risk Management - Madrid 2019 Q1
SR - ITOM - Discovery and Service Mapping - v1.0.35
SR - Security - Integration Framework - Madrid 2019 Q2
SR - Security - Support Common - Madrid 2019 Q2
SR - Security - Support Orchestration - Madrid 2019 Q2
SR - SIR - Security Incident Response - Madrid 2019 Q2
SR - SIR - Security Incident Response PA Content - New York 2019 Q3
SR - SIR - Security Incident Response UI Patch - London 2019 Q2 v.6.2.3
SR - SIR - Splunk Sighting Search Integration - Madrid 2019 Q1
SR - SIR - Store SecOps Setup Assistant - Madrid 2019 Q2
SR - SIR - Store Threat Core - Madrid 2019 Q2
SR - SIR - Store Trusted Security Circles Client - New York 2019 Q3
SR - VR - Qualys - New York 2019 Q3
SR - VR - Rapid7 - London 2019 Q2 v.6.2.1
SR - VR - Vulnerability Response - New York 2019 Q3
SR - VR - Vulnerability Response PA Content - Madrid 2019 Q2

Associated Community Threads

There is no data to report.

Article Information

Last Updated:2019-11-20 14:49:35
Published:2019-05-27