On 29 Mar 2010, at 10:12, Jon mailinglists wrote:
That's why I was talking auth tokens or some other means of
protection.
A guess so, given that auth tokens are an XSRF protection really :)
I suppose more people have thought of that, and this isn't really
Catalyst specific but very
On 20 May 2010, at 00:24, Jeff Albert wrote:
I've never contributed, so I don't know the process, but it would be
nice to see this information in the documentation. If somebody who
knows what's necessary mails me off-list with the information on how
to get started, I would be willing hack
On 13 Jan 2010, at 14:53, Bill Moseley wrote:
Where should this be addressed? In Catalyst or in HTTP::Body?
I'm all for it being addressed as suggested, in both places (for extra
double sure).
Cheers
t0m
___
List: Catalyst@lists.scsys.co.uk
On 1 Mar 2010, at 02:08, Toby Corkindale wrote:
I was thinking it'd be in Module::Install::Catalyst, with some
automatically-added -M options to par.
Yes, that sounds more sane...
Speaking of M-I-C, is there a good reason why STDERR is redirected
to /dev/null, as well as __WARN__?
I
On 18 Dec 2009, at 14:27, Ascii King wrote:
Could you please point out the specific section so I can GO BEAT IT
WITH A STICK. A STICK WITH RUSTY NAILS HAMMERED THROUGH IT. cough
I have done this, the documentation will be more accurate to what we
generally recommend in the next release.
On 19 Jan 2010, at 21:22, Thomas L. Shinnick wrote:
I'm confused about the 'options' to script/foo_create.pl . Nothing
seems to work as documented.
snip
Note already the disagreement between --mechanize and -mechanize.
Fixed in trunk in r13297.
Couldn't load helper
On Fri, May 21, 2010 at 10:24 AM, Tomas Doran bobtf...@bobtfish.net wrote:
On 13 Jan 2010, at 14:53, Bill Moseley wrote:
Where should this be addressed? In Catalyst or in HTTP::Body?
I'm all for it being addressed as suggested, in both places (for extra
double sure).
It's been five
