You are here: Foswiki>Tasks Web>Item12590 (19 Nov 2013, GeorgeClark)Edit Attach

Item12590: Certain exceptions are rendered twice

pencil
Priority: Urgent
Current State: Closed
Released In: 1.1.9
Target Release: patch
Applies To: Engine
Component: FoswikiEngine
Branches: Release01x01 trunk
Reported By: JanKrueger
Waiting For:
Last Change By: GeorgeClark
Any EngineException triggered in individual UI classes (or other switchboard handlers) is sent to the UA by FoswikiUI using $Foswiki::engine->finalizeError. The same Response object is kept alive, though, and later sent to the UA again, this time by $Foswiki::engine->finalize. Since the first go already created headers, the Content-Length header does not match the size of the actual response body generated. In some cases the web server will strip off the superfluous body parts, in others it will retain them – some web servers might mess up the response completely.

This could be considered a bug in either FoswikiUI or FoswikiEngine. The least invasive fix is to change finalizeError so that it empties the response object – that way the later call to finalize will be a no-op.

-- JanKrueger - 02 Oct 2013

 

ItemTemplate edit

Summary Certain exceptions are rendered twice
ReportedBy JanKrueger
Codebase 1.1.8, trunk
SVN Range
AppliesTo Engine
Component FoswikiEngine
Priority Urgent
CurrentState Closed
WaitingFor
Checkins distro:e01083a4ee4c distro:2a212b02d956
TargetRelease patch
ReleasedIn 1.1.9
CheckinsOnBranches Release01x01 trunk
trunkCheckins distro:e01083a4ee4c
Release01x01Checkins distro:2a212b02d956
Topic revision: r5 - 19 Nov 2013, GeorgeClark - This page was cached on 29 Jul 2016 - 12:21.

The copyright of the content on this website is held by the contributing authors, except where stated elsewhere. See Copyright Statement. Creative Commons License