#629: createForwardContainer() doesn't honor the output type completly.
--------------------------+-------------------------------------------------
Reporter: Manuel Giesa | Owner: david
Type: defect | Status: new
Priority: normal | Milestone:
Component: _OTHER_ | Version: HEAD
Severity: normal | Keywords:
--------------------------+-------------------------------------------------
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>
}}}
--
Ticket URL: <http://trac.agavi.org/ticket/629>
Agavi <http://www.agavi.org/>
An MVC Framework for PHP5
_______________________________________________
Agavi Tickets Mailing List
[email protected]
http://lists.agavi.org/mailman/listinfo/tickets
