#1187: Make HTTP Content-Type response header charset detection in
AgaviFormPopulationFilter more robust
--------------------+-------------------------------------------------------
Reporter: david | Owner: david
Type: defect | Status: new
Priority: normal | Milestone: 1.0.2
Component: filter | Version: 1.0.1
Severity: minor | Keywords:
Has_patch: 0 |
--------------------+-------------------------------------------------------
It just matches everything after {{{charset=}}}, while the code that looks
at {{{<meta http-equiv="Content-Type" ... />}}} supports multiple
parameter fragments, quotation marks and so forth.
A matter of simple copy and paste :)
--
Ticket URL: <http://trac.agavi.org/ticket/1187>
Agavi <http://www.agavi.org/>
An MVC Framework for PHP5
_______________________________________________
Agavi Tickets Mailing List
[email protected]
http://lists.agavi.org/mailman/listinfo/tickets
