-Message d'origine-
De : Andy Grundman [mailto:[EMAIL PROTECTED]
Envoyé : mercredi, 28. février 2007 20:30
À : The elegant MVC web framework
Objet : [Catalyst] Please test: Updated HTTP server that
plays nicer with IE
After reworking much of the development HTTP server, I've
Il giorno gio, 01/03/2007 alle 09.27 +0100, Tiziano Faion ha scritto:
in the afternoon i'm working on it.I'll let you know how i solve the
problem.
I've solved, it was easier than what i thought.
In Yaml of both apps i added
cookie_path: '/'
cookie_name: 'something_session'
under
On Thu, Mar 01, 2007 at 04:13:05PM -0800, Bill Moseley wrote:
Seems that Catalyst first tries to match the full path, then tries to
match a reduced path. Adding a bit of debugging to Regex.pm's match()
method:
Request = /training/webcasts/webcast_data/162/foo.html
Checking
i don't think it's a bug.
Catalyst::Manual::Intro also says:
You can pass variable arguments as part of the URL path, separated
with forward slashes (/). If the action is a Regex or LocalRegex, the
'$' anchor must be used. For example, suppose you want to handle /foo/
$bar/$baz, where
this brings up an interesting difference in side-effects of
Catalyst::Log-error() and Log::Log4perl-error().
in the course of trying to integrate catalyst logging with other
existing Log4Perl loggers in the codebase, i had tried first setting
catalyst's logger to be the global logger,
Michael Reece wrote:
i don't think it's a bug.
snip
have you tried adding :Args(0) to the action?
That was my guess too, I've been bit by this problem before adding Args(0) to my
actions.
- Brian
___
List: Catalyst@lists.rawmode.org
