On Fri, 16 Jun 2000, Jim Winstead wrote:
> > > Are you sure about this? I do this all over the place and it
> > > works as documented for me.
> >
> > As documented? As I pointed out before, the documentation is not clear. It
> > never shows $ar->param being called with no arguments in scalar con
On Jun 16, Tom Mornini wrote:
> On Fri, 16 Jun 2000, Jim Winstead wrote:
>
> > On Jun 15, Tom Mornini wrote:
> > > I have recently noticed two issues with Apache::Request and thought I'd
> > > run them by the list before I began hacking and diffing for Doug.
> > >
> > > 1) $ar->param without par
On Fri, 16 Jun 2000, Jim Winstead wrote:
> > 2) [Thu Jun 15 21:09:49 2000] [error] [client 10.50.2.57] [libapreq]
> >unknown content-type: `application/x-www-form-urlencoded;
> >charset=utf-8'
>
> This could probably be fixed by changing the strEQ(ct, DEFAULT_ENCTYPE)
> to ststr(ct, DEFA
On Fri, 16 Jun 2000, Jim Winstead wrote:
> On Jun 15, Tom Mornini wrote:
> > I have recently noticed two issues with Apache::Request and thought I'd
> > run them by the list before I began hacking and diffing for Doug.
> >
> > 1) $ar->param without parameters has different behaviour than CGI.pm
On Jun 15, Tom Mornini wrote:
> I have recently noticed two issues with Apache::Request and thought I'd
> run them by the list before I began hacking and diffing for Doug.
>
> 1) $ar->param without parameters has different behaviour than CGI.pm
>
> Apache::Request returns a reference, CGI.pm r
I have recently noticed two issues with Apache::Request and thought I'd
run them by the list before I began hacking and diffing for Doug.
1) $ar->param without parameters has different behaviour than CGI.pm
Apache::Request returns a reference, CGI.pm returns a list of
parameters.
The man
