<quote who="via RT">
Show quoted text>
> <URL:
http://rt.cpan.org/Ticket/Display.html?id=29187 >
>
> Hi there,
> The encrypted output should actually not be on one line. PayPal is
> nice and will accept it, but the docs say:
>
> "PEM requires that all encoded lines consist of exactly 64 printable
> characters, with the exception of the last line, which may contain
> fewer printable characters. Lines are delimited by whitespace
> characters according to local (platform-specific) conventions."
Ah, I must have missed that. Thanks for taking the time to find it.
Show quoted text>
> Regarding the regexp, it's not stricly necessary but as "," characters
> can't be part of an application/x-www-form-urlencoded payload (they'd
> need to be encoded) anyway, it was done that way for convenience. I
> don't plan on changing the format (as it will break old software) nor
> do I want to add dependencies. I'd want stonger evidence before I
> changed it.
I'll take the , out of my item_name then ;-)
Thanks for your time and replies.
Gavin.
Show quoted text>
> Issac
>
> On Wed Sep 05 10:23:32 2007, GHENRY wrote:
>> Please consider something like Text::CSV_XS.
>>
>> Also, the resulting encrypted data should be all on one line, as per
>> Paypal examples:
>>
>> -----BEGIN PKCS7-----MIIGyg......ILiOUhJpCo=-----END PKCS7-----
> "/></form>
>>
>> There are many newlines, and I'm having to run $encrypted =~ s/\n//g;
> on it.
>>
>> Thanks.
>
> --
>
>