Adam Ness wrote:
> For some odd reason, Apache::URI::hostname is showing up as blank. I've
> tried reading the various man pages and the Oriley book, but I can't
> find any explanation for why hostname would be blank.. Am I overlooking
> something?
yes :) see Reci
For some odd reason, Apache::URI::hostname is showing up as blank. I've
tried reading the various man pages and the Oriley book, but I can't find
any explanation for why hostname would be blank.. Am I overlooking
something?
Thanks in advance.
--
"Write the bad things that
Hey all. I seem to be coming onto the modperl scene a little late, and
it seems one of the classes mentioned in the Eagle book no longer
exists.
I am trying to get the full URI (http(s):///) from
the Apache::URI class. Of course the Eagle mentions that URI::URL is
schedulted to be
On Tue, 14 Aug 2001, Vyacheslav Zamyatin wrote:
> Hello all,
>
>
> Here is a small patch that prevents crash in the following example.
>
>
> $referer = 'http://some.host.com';
> $uri = Apache;:URI->parse($req,$referer);
> $page = $uri->rpath;
&
Geoffrey Young wrote:
>
> > -Original Message-
> > From: Vyacheslav Zamyatin [mailto:[EMAIL PROTECTED]]
> > Sent: Tuesday, August 14, 2001 4:15 AM
> > To: [EMAIL PROTECTED]
> > Subject: bugfix in Apache::URI
> >
> >
> > Hello all,
>
> -Original Message-
> From: Vyacheslav Zamyatin [mailto:[EMAIL PROTECTED]]
> Sent: Tuesday, August 14, 2001 4:15 AM
> To: [EMAIL PROTECTED]
> Subject: bugfix in Apache::URI
>
>
> Hello all,
>
>
> Here is a small patch that prevents crash in the fo
Hello all,
Here is a small patch that prevents crash in the following example.
$referer = 'http://some.host.com';
$uri = Apache;:URI->parse($req,$referer);
$page = $uri->rpath;
If parsed uri don't have path at all, it'll dump core in the last line.
--- URI.x
I'm seeing this problem both under mod_perl 1.25 and 1.26. I've
installed mod_perl as a DSO outside of the Apache source tree using
APXS. It seems to work fine, except for Apache::URI. Here's my
test script:
#!/usr/bin/perl
use strict;
use Apache::FakeRequest;
use Apa
> -Original Message-
> From: Jeffrey W. Baker [mailto:[EMAIL PROTECTED]]
> Sent: Thursday, February 08, 2001 4:47 PM
> To: Nick Tonkin
> Cc: [EMAIL PROTECTED]
> Subject: Re: [RESEND] seg fault with Apache::URI ... weird
>
>
[snip]
just to put everyone on t
On Fri, 9 Feb 2001, Jeffrey W. Baker wrote:
[...]
> Actually, I didn't. Does this mean that strcasecmp(3) on FreeBSD doesn't
> segfault when given NULL pointers? Or does this mean that the version of
> Apache at the time (1.3.6 and 1.3.9) didn't have this problem? The code
> in Apache hasn't
On Fri, 9 Feb 2001, Jeffrey W. Baker wrote:
> On Fri, 9 Feb 2001, Nick Tonkin wrote:
>
> >
> > Hi Jeff,
> >
> > Thanks for your feedback.
> >
> > I wonder if you noticed that this code was from the Auth/Access stuff
> > you did for me a while back ... so I'll patch mine but you might want to
> >
On Fri, 9 Feb 2001, Nick Tonkin wrote:
>
> Hi Jeff,
>
> Thanks for your feedback.
>
> I wonder if you noticed that this code was from the Auth/Access stuff
> you did for me a while back ... so I'll patch mine but you might want to
> take a look at the places you are using it ...
Actually, I didn
Hi Jeff,
Thanks for your feedback.
On Thu, 8 Feb 2001, Jeffrey W. Baker wrote:
> On Thu, 8 Feb 2001, Nick Tonkin wrote:
>
> >
> > Hi all,
> >
> > No response on this so here it is again, any clues appreciated:
> >
> > I am encountering a weird pro
Hi there,
On Thu, 8 Feb 2001, Nick Tonkin wrote:
> No response on this so here it is again, any clues appreciated:
> This code has worked fine for two years or more on my FreeBSD boxes; this
> is on Linux RedHat 7 ... dunno if that makes a difference.
[snip]
> config_args=''
This seems str
On Thu, 8 Feb 2001, Nick Tonkin wrote:
>
> Hi all,
>
> No response on this so here it is again, any clues appreciated:
>
> I am encountering a weird problem with Apache::URI ... consider, please,
> this test handler:
>
> package WM::Test;
>
> use strict;
>
Hi all,
No response on this so here it is again, any clues appreciated:
I am encountering a weird problem with Apache::URI ... consider, please,
this test handler:
package WM::Test;
use strict;
sub handler {
my $r = shift;
my $uri = Apache::URI->parse($r, $r->uri);
er, Test.pm is a ... test script. The seg fault presented itself in real
code :)
~~~
Nick Tonkin
On Sun, 4 Feb 2001, G.W. Haywood wrote:
> Hi there,
>
> On Sun, 4 Feb 2001, Nick Tonkin wrote:
>
> > I am encountering a weird problem with Apache::URI ... consider
Hi there,
On Sun, 4 Feb 2001, Nick Tonkin wrote:
> I am encountering a weird problem with Apache::URI ... consider, please,
> this test handler:
>
> package WM::Test;
[snip]
> As written, this causes a seg fault every time.
I know this will sound strange, but would you, j
Hi all,
I am encountering a weird problem with Apache::URI ... consider, please,
this test handler:
package WM::Test;
use strict;
sub handler {
my $r = shift;
my $uri = Apache::URI->parse($r, $r->uri);
$uri->hostname($r->get_server_name);
$uri->port($r-&
Hello,
I unfortunately still don't understood the API. How can I process e.g.
the URI in a normal perl script that runs under Apache - mod_perl.
I build Apache 1.3.12 (with DSO) and mod_perl 1.22 on Linux 2.3.35.
For example my script: start-page.pl
--
use Apache::URI ();
my $uri
t, unless the request is a proxy
request.
> But, if instead I do,
>
> my $me = Apache::URI->parse($r);
that's a shortcut for building "self urls", if you don't specify a url,
the Apache::URI is filled in with everything it can dig out of the
request object (including scheme/hostname/port)
nd
only $r_path and $r_rpath have data in them (and the data is correct).
But, if instead I do,
my $me = Apache::URI->parse($r);
my $r_scheme = $parsed_uri->scheme;
my $r_host = $parsed_uri->hostinfo;
my $r_rpath= $parsed_uri->rpath;
my $r_path = $parsed_uri->path;
It works! Thanks so much!
Fred
Eric Cholet wrote:
> > Hello,
> >
> > It seems the method unparse() of Apache::URI does not take the port
> > value into the result string. For example, I have:
> >
> > my $uri = Apache::URI->parse($r, $r->uri);
> &g
> Hello,
>
> It seems the method unparse() of Apache::URI does not take the port
> value into the result string. For example, I have:
>
> my $uri = Apache::URI->parse($r, $r->uri);
> $uri->scheme('http');
> $uri->hostname($r->get_server_nam
Hello,
It seems the method unparse() of Apache::URI does not take the port
value into the result string. For example, I have:
my $uri = Apache::URI->parse($r, $r->uri);
$uri->scheme('http');
$uri->hostname($r->get_server_name);
$uri->port(8080);
$uri->que
0 9:24 AM
> To: '[EMAIL PROTECTED]'
> Cc: '[EMAIL PROTECTED]'; '[EMAIL PROTECTED]'
> Subject: Apache::URI troubles
>
>
> hi all...
>
> I found the below discussion in the archives... while Doug's
> suggestion helps fill in some
L PROTECTED] I can't seem to get at the
user/pass combo, either by parsing hostinfo myself or using the user() and
password() methods. All hooks are enabled - is there something else I
should be looking for?
PerlTransHandler snippet:
use Apache::URI;
use strict;
sub handler {
my $r
Looks like you did not build mod perl with Apache::URI.
Your Apache::WebSQL is attempting to dynamically load it, but
the module is not available.
You probably need to rebuild mod_perl with EVERYTHING. see
the faq or the perl.apache.org/guide.
cliff rayman
genwax.com
Joe Ryan wrote:
> I
I am getting the following error when trying to
use Apache::URI
---
[Thu Dec 16 11:52:28 1999] [error] Apache::WebSQL: `Can't locate loadable object for
module Apache::URI in @INC (@INC contains: . /sysdev/web/a
29 matches
Mail list logo
