createForwardContainer() doesn't honor the output type completly.

[Manuel Giesa]

If i use a forward container to forward to another output type, the http-headers aren't set for the target output type and the old ones are kept. In the following case the 404 XML will be delivered as application/octet-stream.

public function executeBinary(AgaviRequestDataHolder $rd) {
    return $this->createForwardContainer(AgaviConfig::get('action.error_404.module'),     
                                  AgaviConfig::get('action.error_404.action'), array(), 'xml');
}

Releveant settings for both output types: xml:

<parameter name="Content-Type">application/xml; charset=UTF-8</parameter>

binary:

<parameter name="Content-Type">application/octet-stream</parameter>

[david]

Reproduce case. Call /login.txt too see the issue.

[david]

(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.