Jason Kohles wrote:
On Jan 29, 2008, at 3:18 AM, Kieren Diment wrote:
On 27 Jan 2008, at 20:59, Ian Docherty wrote:
p.s. I note that there is nothing in Test::WWW (that I can find)
that tests return status's such as 200, 401 etc.
From perldoc Test::WWW::Mechanize:
...
From perldoc W
On Jan 29, 2008, at 3:18 AM, Kieren Diment wrote:
On 27 Jan 2008, at 20:59, Ian Docherty wrote:
p.s. I note that there is nothing in Test::WWW (that I can find)
that tests return status's such as 200, 401 etc.
From perldoc Test::WWW::Mechanize:
...
From perldoc WWW::Mechanize:
...
On 27 Jan 2008, at 20:59, Ian Docherty wrote:
p.s. I note that there is nothing in Test::WWW (that I can find)
that tests return status's such as 200, 401 etc.
From perldoc Test::WWW::Mechanize:
Test::WWW::Mechanize is a subclass of WWW::Mechanize that incorporates
features for
On Sat, 26 Jan 2008, Ian Docherty wrote:
Related to my earlier thread about basic authentication, what do I have to do
to return a 401 error from within Catalyst?
I have tried to understand the documentation at
http://www.ietf.org/rfc/rfc2617.txt but it does not help me in a practical
mann
Ian Docherty wrote:
Related to my earlier thread about basic authentication, what do I
have to do to return a 401 error from within Catalyst?
I have tried to understand the documentation at
http://www.ietf.org/rfc/rfc2617.txt but it does not help me in a
practical manner.
My understanding i
Related to my earlier thread about basic authentication, what do I have
to do to return a 401 error from within Catalyst?
I have tried to understand the documentation at
http://www.ietf.org/rfc/rfc2617.txt but it does not help me in a
practical manner.
My understanding is that when the Catal
