Tickets :: [#10740] Reuse of Horde HTTP request object leads to weird side effects

Summary	Reuse of Horde HTTP request object leads to weird side effects
Queue	Kronolith
Queue Version	3.0.11
Type	Bug
State	Resolved
Priority	2. Medium
Owners	jan (at) horde (dot) org
Requester	christof (at) buergi (dot) lugs (dot) ch
Created	11/12/2011 (4941 days ago)
Due
Updated	11/14/2011 (4939 days ago)
Assigned
Resolved	11/14/2011 (4939 days ago)
Milestone	3.0.12
Patch	Yes

11/14/2011 03:37:31 PM	Jan Schneider	Assigned to Jan Schneider State ⇒ Resolved Milestone ⇒ 3.0.12

11/14/2011 03:37:21 PM	Git Commit	Comment #2	Reply to this comment
Changes have been made in Git for this ticket: Don't re-use Horde_Http_Client instances, they leak (~~Bug #10740~~). 3 files changed, 5 insertions(+), 5 deletions(-) http://git.horde.org/horde-git/-/commit/d26a8a9036edc53ffe02cd0522a1f776dd0b2fde

11/12/2011 06:01:56 PM	christof (at) buergi (dot) lugs (dot) ch	Comment #1 Priority ⇒ 2. Medium New Attachment: Ical.patch Patch ⇒ Yes Milestone ⇒ Queue ⇒ Kronolith Summary ⇒ Reuse of Horde HTTP request object leads to weird side effects Type ⇒ Bug State ⇒ Unconfirmed	Reply to this comment
Kronolith tries to reuse a Horde HTTP request object, once it got one. Unfortunately, the request object is not really built to be reused. Thus we get weird effects like GET requests with additional data (from the last request) or premature timeout errors.