in reply to Re^2: LWP::Curl and character encoding
in thread LWP::Curl and character encoding

I take it that using 'get' is out....and I need to just not use the Curl interface?

I don't see why that would be the case. Simply RTFM so you can get at the headers

Replies are listed 'Best First'.
Re^4: LWP::Curl and character encoding
by perl-diddler (Chaplain) on Nov 16, 2010 at 13:16 UTC
    RTFM?

    Is there a manual that describes how to get to headers, or are you sugggesting I hack the Curl source?

    At that point, I might as well use an alternate interface it seems.

      Is there a manual that describes how to get to headers, or are you sugggesting I hack the Curl source?

      Wait, why did you pick curl?

      This module provides a Perl interface to libcurl. It is not intended to be a standalone module and because of this, the main libcurl documentation should be consulted for API details at http://curl.haxx.se. The documentation you're reading right now only contains the Perl specific details, some sample code and the differences between the C API and the Perl one.

      http://cpansearch.perl.org/src/ANDREMAR/WWW-Curl-Simple-0.100181/lib/WWW/Curl/Simple/Request.pm

      my ($body_ref, $head_ref); $self->body(\$body_ref); $self->head(\$head_ref); open (my $fileb, ">", \$body_ref); $curl->setopt(CURLOPT_WRITEDATA,$fileb); my $h = $self->head; open (my $fileh, ">", \$head_ref); $curl->setopt(CURLOPT_WRITEHEADER,$fileh); return $curl; sub response { my ($self) = @_; my $res = HTTP::Response->parse(${$self->head} . "\r" . ${$self->b +ody}); $res->request($self->request); $res->content(${$self->body}); return $res; }
      http://search.cpan.org/grep?cpanid=SZBALINT&release=WWW-Curl-4.14&string=CURLOPT_WRITEHEADER&i=1&n=1&C=12
        At the time I picked curl as it had the simplest interface -- a 'get'.

        No other reason.