Skip Menu |

Preferred bug tracker

Please visit the preferred bug tracker to report your issue.

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

Report information
The Basics
Id: 41358
Status: resolved
Priority: 0/
Queue: Net-Amazon-S3

People
Owner: Nobody in particular
Requestors: simon [...] browsing.co.uk
Cc:
AdminCc:

Bug Information
Severity: (no value)
Broken in: (no value)
Fixed in: (no value)



Subject: uppercase bucket IDs (via brackup)
Date: Mon, 1 Dec 2008 20:48:41 +0000
To: bug-Net-Amazon-S3 [...] rt.cpan.org
From: Simon Elliott <simon [...] browsing.co.uk>
I'm not sure whether this should be classed as a bug, but it will certainly be a problem due to the improved constraints on bucket names in the latest version. Brackup by default uses AWSID-backup (your awsID is uppercase) which apparently Amazon supports despite claiming otherwise. Unfortunately when they want to get to their backups now this module (correctly) disallows the name, but it might be simpler to just allow A-Z in the interim while Brackup is patched and people pass their backups to the new bucket name. Also, the type constraint always displays the same error (IP address regexp) despite the constraint failing in a different block. Thanks Simon.
Thanks for the bug report, I asked Amazon: http://developer.amazonwebservices.com/connect/thread.jspa?threadID=26930 and then have released Net-Amazon-S3-0.48.tar.gz to CPAN: 0.48 Thu Dec 4 09:24:23 GMT 2008 - be slightly less strict about bucket names: they can contain uppercase letters, Amazon just doesn't recommend it (noticed by Simon Elliott, fixes Brackup)