Skip Menu |

This queue is for tickets about the Amazon-S3 CPAN distribution.

Report information
The Basics
Id: 40281
Status: open
Priority: 0/
Queue: Amazon-S3
People
Owner: tima [...] cpan.org
Requestors: mbollinger [...] gmail.com
Cc:
AdminCc:
Bug Information
Severity: Important
Broken in: 0.441
Fixed in: (no value)

History Show all quoted text
  Wed Oct 22 18:21:41 2008 mbollinger [...] gmail.com - Ticket created
Hi, I've noticed that in the get_key() method for Bucket.pm, it calls _croak_if_response_error(). While it's nice that the error is reported back, Amazon returns a handful HTTP error codes for many different error conditions, most of which shouldn't necessarily be fatal. Perhaps from the view of a library, the best approach may be to set an error flag in the response object, and leave the user to interpret the response codes themselves, instead of croaking. Thanks!
  Fri Aug 14 21:07:42 2009 tima [...] cpan.org - Taken
  Fri Aug 14 21:09:13 2009 tima [...] cpan.org - Correspondence added
Subject: Amazon-S3
Sorry for the incredibly long delay. Do you have a patch for this? Amazon-S3 is a fork of Net::Amazon::S3 and is where this practice stems from. I'm open to changing it. <tim/> On Wed Oct 22 18:21:41 2008, mbollinger wrote: Show quoted text
> Hi, I've noticed that in the get_key() method for Bucket.pm, it calls > _croak_if_response_error(). While it's nice that the error is reported > back, Amazon returns a handful HTTP error codes for many different error > conditions, most of which shouldn't necessarily be fatal. Perhaps from > the view of a library, the best approach may be to set an error flag in > the response object, and leave the user to interpret the response codes > themselves, instead of croaking. Thanks!
  Fri Aug 14 21:09:14 2009 The RT System itself - Status changed from 'new' to 'open'