Lionel Cons <[EMAIL PROTECTED]> writes:
> I would need partial HTTP/1.1 support in order to have "keep alive"
> connections for a web proxy. It seems that libwww-perl 5 is almost up
> to the task because Bob McElrath's FilterProxy version 0.29 claims to
> work like that (see http://draal.physics.
>From the README:
This is the HTML-Parser distribution with shared libraries
compiled for
MacPerl. Shared libraries run only on PPC and CFM68K versions,
not non-CFM
68K versions.
The original of the changed files are in Mac_changed.sit.
This was compiled with Codewarrior IDE.
All tests pass
> "Dave" == Dave Faraldo <[EMAIL PROTECTED]> writes:
Dave> Yup, you got it. Override LWP::UserAgent::redirect_ok with the
Dave> following, and you should be golden:
Dave> # Overloaded function to allow GET redirects following POSTs
Dave> sub redirect_ok {
Dave> my ($ua, $req) = @_;
I'm trying to determine, using LWP, Crypt::SSLeay, or whatever tools I need
to use, what the expiration date of a remote server certificate is.
For example, if I connect to edit.secure.yahoo.com, I'll get back as headers:
HTTP/1.1 200 OK
Cache-Control: private
Connection: close
Date: Fri, 16 Mar
Hi all,
Some particulars ...
perl 5.005_03 built for alpha-dec_osf
LWP 5.50
URI 1.11
The skinny is that I cant get the "type=a" parameter to work for
ftp:// urls. I see that the check for "type=a" is commented out
around line 120 of LWP/Protocol/ftp.pm.
I will check some more on
> I think you can subclass the post request with one new function that
> says to follow redirects, but I haven't tried that yet.
Yup, you got it. Override LWP::UserAgent::redirect_ok with the
following, and you should be golden:
# Overloaded function to allow GET redirects following POSTs
[EMAIL PROTECTED] writes:
> Is there any way URI could [re]acquire the params() method and
> Protocol::ftp check for "type=a"? ;>
I think this patch should fix the problem.
Regards,
Gisle
Index: lib/LWP/Protocol/ftp.pm
===
RCS fi
On Thu, 15 Mar 2001, Cormac Garvey wrote:
> Hi,
> I am new to libwww. I want to use libwww to acess my bank A/C's and
> Stocks via a client program.
So am I, so I figured this one out last night.
> HTTP/1.1 302 (Found) Moved Temporarily
> Date: Thu, 15 Mar 2001 21:53:36 GMT
> Location: /ft
Hi,
I am new to libwww. I want to use libwww to acess my bank A/C's and
Stocks via a client program.
initially I tryed to access my Fidelity A/C.
Here is my code.
#!/usr/bin/perl
use LWP::UserAgent;
my $ua = LWP::UserAgent->new;
#
my $req = HTTP::Request->new(POST =>
'https://webxpr
On Wed, Mar 14, 2001 at 02:23:24PM -0800, Jeff Orrok wrote:
> I don't understand why there is an -arch i386 in
> LD_RUN_PATH, and if I was supposed to remove it, why didn't the README
> tell me so?
It's a bug in the perl install on Mac OS X Server ...
edit /System/Library/Perl/rhapsody/Config.pm
[Seems like Gnus' MIME composition support is a bit flaky, so let me redo
the message without the MIMEs.]
A new release of libwww-perl should now be on CPAN. This release
contains an important security fix for those that use LWP from CGI
scripts. It is recommended that everybody that use LWP::U
Index: lib/LWP/UserAgent.pm
===
RCS file: /cvsroot/libwww-perl/lwp5/lib/LWP/UserAgent.pm,v
retrieving revision 1.74
retrieving revision 1.77
diff -u -p -u -r1.74 -r1.77
--- lib/LWP/UserAgent.pm 2000/06/01 13:35:15 1.74
+++ lib/LWP/Use
Lillith Lesanges wrote:
>
> On Wed, 14 Mar 2001, Jeff Orrok wrote:
>
> > Hello, I'm a perl library newbie trying to get libwww-perl set up on an
> > OS X Server platform, and I'm getting the following error trying to
> > install MIME::Base64. I don't understand why there is an -arch i386 in
> >
Hi all ...
Well, I tracked it down to $remote_file becoming a reference to
a URI::_segment object somehow when there is a ;parameter in the
url. With "print $response->as_string" I get:
500 (Internal Server Error) Can't locate object method "path" via \
package "URI::_segment"
Client-Date:
Hi all,
slightly OT here but does this
> Extensive testing of current client applications demonstrated that
> the majority of deployed systems do not use the ";" character to
> indicate trailing parameter information, and that the presence of a
> semicolon in a path segment does not affect the r
Hi all, (did anyone get this the first time?)
Some particulars ...
perl 5.005_03 built for alpha-dec_osf
LWP 5.50
URI 1.11
The skinny is that I cant get the "type=" parameter to work for
ftp:// urls. I see that the check for "type=a" is commented out
around line 120 of LWP/Protoc
Hi there!
I would need partial HTTP/1.1 support in order to have "keep alive"
connections for a web proxy. It seems that libwww-perl 5 is almost up
to the task because Bob McElrath's FilterProxy version 0.29 claims to
work like that (see http://draal.physics.wisc.edu/FilterProxy/).
Looking at his
17 matches
Mail list logo
