[Catalyst-dev] HTTP::Body not storing raw bodies of UrlEncoded requests (RT #111876) - opinions requested

John Napiorkowski jjn1056 at yahoo.com
Tue Feb 9 01:30:07 GMT 2016


Not sure the devs for this monitor this mailing list.  Maybe try IRC or emailing the last person to release directly?


On Monday, February 8, 2016 6:05 PM, David Precious <davidp at preshweb.co.uk> wrote:

Hi folks,

I have a problem with HTTP::Body not returning the raw body content for
responses parsed by the UrlEncoded parser, which is causing us a
problem in Dancer1:


My preferred fix for this is for HTTP::Body::UrlEncoded to stash the
body being parsed away in a temp file as the other parsers already do -
which I've submitted as a patch in RT #111876:


First off - do you consider that sensible, and would you consider
applying it and getting a new HTTP::Body release out - and if so, would
that be likely to be doable in the near future?  (If you agreed with
the change but don't have time to maintain HTTP::Body or get new
releases out, I may be willing to step up as a co-maint and clear some
of the older tickets in the queue too perhaps.)

Alternatively - if you don't agree with my proposed change, or don't
think a new release with it in could be forthcoming for some time,
would you have any objections to me bundling up my modified version of
HTTP::Body as Dancer::HTTP::Body and shipping it with Dancer
(maintaining the licencing/author information and with PAUSE told not
to index it)?


Dave P (bigpresh)

Catalyst-dev mailing list
Catalyst-dev at lists.scsys.co.uk

More information about the Catalyst-dev mailing list