why doesn"t getstore function well on freebsd?

Hi;

I have a small program that uses getstore to fetch a xml webpahe and
store it. It is:

use strict;
use warnings;

use LWP::Simple;

my $xmlurl=3D"http://www.sec.gov/Archives/edgar/data/903404/000 118143105029=
692/rrd79736.xml";
my $xmlfile=3D"xml.xml";
my $status=3Dgetstore($xmlurl,$xmlfile);

if(is_success($status))
{
print "xmlfile store is ok\n";
}
else
{
print "xmlfile store isn't ok\n";
}


It works well on windows platform, but doesn't on freebsd. That is,
every time the getstore function's response is "200 ok", but the
stored xml file isn't correct, it means, it isn't as same as the xml
webpage. What is wrong with it? And is there any solution or
alternatives to this problems?

Thank you very much!

Best wishes
Franklin

Re: why doesn"t getstore function well on freebsd?

On Tue, May 24, 2005 at 03:07:24PM +0800, Franklin wrote:

> my $xmlurl="http://www.sec.gov/Archives/edgar/data/903404/00011 8143105029692/rrd79736.xml";
> my $xmlfile="xml.xml";
> my $status=getstore($xmlurl,$xmlfile);

> It works well on windows platform, but doesn't on freebsd. That is,
> every time the getstore function's response is "200 ok", but the
> stored xml file isn't correct, it means, it isn't as same as the xml
> webpage.

This sounds more like a problem with your setup. (Transparent) Proxy
cache somewhere maybe? Is the timestamp updated?

\rho

Re: why doesn"t getstore function well on freebsd?

I will do further research according to your suggestions. Thank you very mu=
ch!=20


On 5/25/05, Robert Barta wrote:
> On Tue, May 24, 2005 at 03:07:24PM +0800, Franklin wrote:
>=20
> > my $xmlurl=3D"http://www.sec.gov/Archives/edgar/data/903404/000 11814310=
5029692/rrd79736.xml";
> > my $xmlfile=3D"xml.xml";
> > my $status=3Dgetstore($xmlurl,$xmlfile);
>=20
> > It works well on windows platform, but doesn't on freebsd. That is,
> > every time the getstore function's response is "200 ok", but the
> > stored xml file isn't correct, it means, it isn't as same as the xml
> > webpage.
>=20
> This sounds more like a problem with your setup. (Transparent) Proxy
> cache somewhere maybe? Is the timestamp updated?
>=20
> \rho
>