Ticket #633 (closed task: fixed)

Opened 12 months ago

Last modified 12 months ago

Check if global request data is supposed to be serialized with execution containers

Reported by: david Owned by: david
Priority: normal Milestone: 0.11.1
Component: controller Version: 0.11.0
Severity: normal Keywords:
Cc: Patch attached:

Description

check [2115] and compare [2114] and [2108]

Attachments

Change History

Changed 12 months ago by david

  • status changed from new to assigned

it's not :)

Changed 12 months ago by david

  • status changed from assigned to closed
  • resolution set to fixed

(In [2205]) Fixed an issue where output types of forwards were not honored completely. Closes #629. Also redone the global request data locking during template rendering and fixed global request data serialization in execution containers. Closes #628 and #633. This change adds an output type member to response. Use that to check for the actual response content type, not the one in the execution container - it's more reliable. See changes done to FPF and ETF in this commit.

Add/Change #633 (Check if global request data is supposed to be serialized with execution containers)

Author



Action
as closed
Next status will be 'reopened'
 
Note: See TracTickets for help on using tickets.