Loading ...
Sorry, an error occurred while loading the content.

S::T::H::Client 0.60 and Content-Encoding

Expand Messages
  • mihai_razvan
    Hi list, could someone please explain why SOAP::Transport:HTTP::Client chooses to C whenever it receives a Content-Encoding header (not using compression)
    Message 1 of 1 , Feb 1, 2005
    • 0 Attachment
      Hi list,

      could someone please explain why SOAP::Transport:HTTP::Client chooses
      to C<die> whenever it receives a Content-Encoding header (not using
      compression) ?

      I'm referring to this piece of code in C<send_receive>:

      # start code

      my $content =
      ($resp->content_encoding || '')
      =~ /\b$SOAP::Transport::HTTP::Client::COMPRESS\b/o &&
      $self->options->{is_compress} ?
      Compress::Zlib::memGunzip($resp->content)
      : ($resp->content_encoding || '') =~ /\S/
      ? die "Can't understand returned Content-Encoding (@{[$resp-
      >content_encoding]})\n"
      : $resp->content;
      $resp->content_type =~ m!^multipart/!
      ? join("\n", $resp->headers_as_string, $content) : $content;

      # end code

      Thanks for your time,

      Razvan
    Your message has been successfully submitted and would be delivered to recipients shortly.