Re: Problem using URI-1.22...

On Fri, 22 Nov 2002, Michael A Chase wrote: > I cut and pasted your code into the following script and it works for me > (URI-1.21). It should work with URI-1.22 since I don't see any changes in > URI.pm that would affect this. > > #!/usr/bin/perl -w > use URI; > u

Re: Problem using URI-1.22...

no 'use strict;' and '-w' in the '#!' line? Try single stepping into URI->new() with the Perl debugger. It's all Perl code, so you ought to be able to find out why the 'http:' scheme in the URI isn't getting picked up and converted to the appropria

Problem using URI-1.22...

Hi, I'm trying to pass a url like: http://link.clientname.com/path_name And get: Can't locate object method "host" via package "URI::_generic" at ../buggy_program.pl line 17. I'm using: $url_use = "http://link.clientname.com/path_name"; $url = URI->new($url_use); $host_name = $url->host();

Test failure with URI 1.22

With both Perl 5.6.1 and 5.8.0, I receive the following output when running `perl -Iblib/lib t/file.t' for URI 1.22: 1..12 ok 1 ok 2 ok 3 ok 4 URI->new('file://foo/bar', 'file')->file('unix') ne //foo/bar, but /bar URI->new('file://foo/bar',

delimeter instance variable for scalarref object (Was: URI-1.22)

I've been off on vacation, then sick, but am now catching up on email and I saw this: 2002_09_03 [EMAIL PROTECTED] wrote: > How about an option to someway tell query_param to use > (if not default to) ";" as the separator in query strings > instead of "&"? 2002_09_03 [EMAIL PROTECTED] wrote:

Re: URI-1.22

[EMAIL PROTECTED] writes: > Gisle Aas <[EMAIL PROTECTED]> wrote: > > > > > You want to extend the new query_param() in some way? > > > > > > I was thinking about $u->query_param(';', foo => 0..3), ie. taking the > > > first arg as the separator. But I'm not sure if this is actually better > >

Re: URI-1.22

Gisle Aas <[EMAIL PROTECTED]> wrote: > > > You want to extend the new query_param() in some way? > > > > I was thinking about $u->query_param(';', foo => 0..3), ie. taking the > > first arg as the separator. But I'm not sure if this is actually better > > than the former suggestion at all. > >

RE: URI-1.22

-Original Message- From: Gisle Aas [mailto:[EMAIL PROTECTED]] Sent: Tuesday, September 03, 2002 10:48 PM To: Keary Suska Cc: Libwww Perl Subject: Re: URI-1.22 Keary Suska <[EMAIL PROTECTED]> writes: > I don't wish to complicate issues any, but it seems to me mo

Re: URI-1.22

Keary Suska <[EMAIL PROTECTED]> writes: > I don't wish to complicate issues any, but it seems to me more sensible to > specify the desired separator string as an optional parameter to the URI > constructor. I think this is a clever hack. If instead of constructing objects of the URI class you c

Re: URI-1.22

Keary Suska <[EMAIL PROTECTED]> writes: > I don't wish to complicate issues any, but it seems to me more sensible to > specify the desired separator string as an optional parameter to the URI > constructor. This also avoids the mentioned caveats, as it would otherwise > have to be explicitly chan

Re: URI-1.22

I don't wish to complicate issues any, but it seems to me more sensible to specify the desired separator string as an optional parameter to the URI constructor. This also avoids the mentioned caveats, as it would otherwise have to be explicitly changed. I recall there was a question of instance va

Re: URI-1.22

Ville Skyttä <[EMAIL PROTECTED]> writes: > On Wed, 2002-09-04 at 01:05, Gisle Aas wrote: > > > > However, if the query_param method interface has been there for only a > > > couple of days now, perhaps it wouldn't be impossible to change it to > > > have the sepchar there and quickly release URI

Re: URI-1.22

On Wed, 2002-09-04 at 01:05, Gisle Aas wrote: > > However, if the query_param method interface has been there for only a > > couple of days now, perhaps it wouldn't be impossible to change it to > > have the sepchar there and quickly release URI-1.23. > > The sepchar proposal as it stands now is

Re: URI-1.22

On Wed, 2002-09-04 at 01:07, Sean M. Burke wrote: > Personally, I think the W3C's whole ;-for-& idea is something that should > have been done from the beginning, but which it's maybe too late to do now > -- since one never knows if a given server/CGI will be able to make sense > of ;-as-separ

Re: URI-1.22

At 08:43 2002-09-03 -0700, Gisle Aas wrote: >Some have suggested that $u->query_form should just split on both >[&;]. I have two problems with that; 1) I'm not totally convinced >that URIs like ?foo=1;2;3&bar=1 does not exist and 2) how do we know >what to use for joining parameters. Personally,

Re: URI-1.22

Ville Skyttä <[EMAIL PROTECTED]> writes: > > $u->query_param(foo => 1); > > print $u; # prints "?foo=1" > > print $u->query-sepchar; # prints "&" > > > > $u->query_param(foo => 1..3); > > print $u; # prints "?foo=1;foo=2;foo=3" > > Shouldn't

Re: URI-1.22

On Tue, 2002-09-03 at 22:56, Gisle Aas wrote: > > > Some have suggested that $u->query_form should just split on both > > > [&;]. I have two problems with that; 1) I'm not totally convinced > > > that URIs like ?foo=1;2;3&bar=1 does not exist and > > > > Hmm. I wonder if anything that accepts

Re: URI-1.22

Ville Skyttä <[EMAIL PROTECTED]> writes: > > Some have suggested that $u->query_form should just split on both > > [&;]. I have two problems with that; 1) I'm not totally convinced > > that URIs like ?foo=1;2;3&bar=1 does not exist and > > Hmm. I wonder if anything that accepts both of delimit

Re: URI-1.22

On Tue, 2002-09-03 at 18:43, Gisle Aas wrote: > > How about an option to someway tell query_param to use (if not default > > to) ";" as the separator in query strings instead of "&"? > > I actually thought a bit about that when I did URI::QueryParam, but I > did not manage to come up with an API

Re: URI-1.22

On Tue, 2002-09-03 at 10:36, Sean M. Burke wrote: > >- > > I wonder -- is that ;-for-& thing specified in some RFC too? Well, the only one I'm aware of is RFC 1866 (HTML 2.0), section 8.2.1. Don't know if that counts as a useful refere

Re: URI-1.22

Ville Skyttä <[EMAIL PROTECTED]> writes: > How about an option to someway tell query_param to use (if not default > to) ";" as the separator in query strings instead of "&"? I actually thought a bit about that when I did URI::QueryParam, but I did not manage to come up with an API that I liked.

Re: URI-1.22

At 09:16 2002-09-03 +0300, Ville Skyttä wrote: >[...]More info: >- I wonder -- is that ;-for-& thing specified in some RFC too? -- Sean M. Burkehttp://www.spinn.net/~sburke/

Re: URI-1.22

> URI-1.22 is now propegating on CPAN. New since last release is sip: > and sips: support contributed by Ryan Kereliuk and a URI::QueryParam > module that does this: Cool. > SYNOPSIS > use URI; > use URI::QueryParam; > > $u = URI->new("",

URI-1.22

URI-1.22 is now propegating on CPAN. New since last release is sip: and sips: support contributed by Ryan Kereliuk and a URI::QueryParam module that does this: NAME URI::QueryParam - Additional query methods for URIs SYNOPSIS use URI; use URI::QueryParam; $u = URI->