[
https://issues.apache.org/jira/browse/VELOCITY-721?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Aruna Venkataraman closed VELOCITY-721.
---------------------------------------
Resolution: Invalid
By handle i meant, catching this exception and redirecting the user to a user friendly error page.
Since this exception is not applicable to velocity as it isn't web centric i am closing this issue as invalid. Sorry for the inconvenience.
Regards,
Aruna
> Handle the exception HTTP Error 413 - Request entity too large in the exceptions section of Velocity engine
> -----------------------------------------------------------------------------------------------------------
>
> Key: VELOCITY-721
> URL:
https://issues.apache.org/jira/browse/VELOCITY-721> Project: Velocity
> Issue Type: Improvement
> Components: Engine
> Affects Versions: 1.6.1
> Environment: Windows XP, j2sdk1.4.2_13,
> Reporter: Aruna Venkataraman
> Fix For: 1.6.2
>
> Original Estimate: 16h
> Remaining Estimate: 16h
>
> The following exceptions are currently handled in velocity engine:
> 1. ExtendedParseException
> 2. MacroOverflowException
> 3. MathException
> 4. MethodInvocationException
> 5. ParseErrorException
> 6. ResourceNotFoundException
> 7. TemplateInitException
> I suggest that another exception RequestEntityTooLarge also be handled by the velocity engine. When the client requests an entity that is too large from the application hosted on the web server, the server throws "Request Entity Too Large" exception with the status code 413.
> Can this HTTP 413 Request Entity Too Large exception be handled in velocity engine? Please let me know if this suggestion is beneficial. I am frequently getting this error which could be handled.
> Regards,
> Aruna
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
---------------------------------------------------------------------
To unsubscribe, e-mail:
dev-unsubscribe@...
For additional commands, e-mail:
dev-help@...
