logo
Free, unlimited AI code reviews that run on commit
git-lrc git-lrc GitHub Install Now We'd appreciate a star git-lrc - Free, unlimited AI code reviews that run on commit | Product Hunt git-lrc - Free, unlimited AI code reviews that run on commit | Product Hunt

URI::Fetch::Response - Feed response for URI::Fetch

Description

URI::Fetch::Response encapsulates the response from fetching a feed using URI::Fetch.

Name

       URI::Fetch::Response - Feed response for URI::Fetch

Synopsis

           use URI::Fetch;
           my $res = URI::Fetch->fetch('http://example.com/atom.xml')
               or die URI::Fetch->errstr;
           print $res->content;

Usage

$res->content
       The contents of the feed.

   $res->uri
       The URI of the feed. If the feed was moved, this reflects the new URI; otherwise, it will match the URI
       that you passed to fetch.

   $res->etag
       The ETag that was returned in the response, if any.

   $res->last_modified
       The Last-Modified date (in seconds since the epoch) that was returned in the response, if any.

   $res->status
       The status of the response, which will match one of the following enumerations:

       •   URI::Fetch::URI_OK()URI::Fetch::URI_MOVED_PERMANENTLY()URI::Fetch::URI_GONE()URI::Fetch::URI_NOT_MODIFIED()$res->http_status
       The HTTP status code from the response.

   $res->http_response
       The HTTP::Response object returned from the fetch.

   $res->is_success$res->is_redirect$res->is_error
       Wrappers around the "$res->response" methods of the same name, for convenience.

       Note:  there  is one difference from the behaviour of HTTP::Response.  If you are using a cache and get a
       304 response, but the data is retrieved from the cache,  then  "is_success"  will  return  true,  because
       "res->content" is usable.

   $res->content_type
       The Content-Type header from the response.

See Also