On 6 Feb 2009, at 17:36, Bill Moseley wrote:
Sure. IIRC, I think there's already been some patches and code posted
so maybe I can dig that up again off the archives.
Please do.
But, sounds like
it's not that important of an issue.
The fact that nobody is working on it currently is not
On 6 Feb 2009, at 14:46, Bill Moseley wrote:
Nobody responded to the main point of this email -- if Catalyst should
handle encoding in core instead of with a plugin. Nobody has an
opinion about that? Or is was it just ignored -- which is often how
people handle character encoding in
On Fri, Jan 30, 2009 at 11:44:57PM +0100, Aristotle Pagaltzis wrote:
* Bill Moseley mose...@hank.org [2009-01-29 17:05]:
Neither of the existing plugins do it correctly (IMO), as
they only decode parameters leaving body_parameters as octets,
and don't look at the request for the charset,
On Fri, Feb 06, 2009 at 03:16:14PM +, Tomas Doran wrote:
On 6 Feb 2009, at 14:46, Bill Moseley wrote:
Nobody responded to the main point of this email -- if Catalyst should
handle encoding in core instead of with a plugin. Nobody has an
opinion about that? Or is was it just ignored --
* Bill Moseley mose...@hank.org [2009-01-29 17:05]:
Neither of the existing plugins do it correctly (IMO), as
they only decode parameters leaving body_parameters as octets,
and don't look at the request for the charset, IIRC. […]
uri_for() rightly encodes to octets before escaping, but it
