One comment I forgot to make. If you do not specify a boundary when creating the form HTTP::Request::Common creates one for you. In my case, the boundary it created could possible have appeared in the payload. (PGP encrypted file) The boundary created by HTTP:Common::REquest ends up not being enclosed in quotes.
-----Original Message----- From: Keith C. Ivey [mailto:[EMAIL PROTECTED] Sent: Saturday, March 15, 2003 8:57 AM To: [EMAIL PROTECTED] Subject: RE: HTTP::Request::Common Costa, Michael J. <[EMAIL PROTECTED]> wrote: > I'm working on a project > for the utility industry and we have a new company that we are > dealing with and they took the spec we are working from quite > literally. They cannot deal with the boundary spec being > enclosed in quotes. (It really shouldn't be anyway.) It needn't be enclosed in quotes (with the specific boundary you're using), but it's not true that it shouldn't be. In fact RFC 2046 mentions it specifically: | WARNING TO IMPLEMENTORS: The grammar for parameters on | the Content-type field is such that it is often necessary | to enclose the boundary parameter values in quotes on the | Content-type line. This is not always necessary, but never | hurts. So the behavior of HTTP::Request::Util is not a bug. -- Keith C. Ivey <[EMAIL PROTECTED]> Washington, DC _______________________________________________ Perl-Win32-Web mailing list [EMAIL PROTECTED] To unsubscribe: http://listserv.ActiveState.com/mailman/mysubs _______________________________________________ Perl-Win32-Web mailing list [EMAIL PROTECTED] To unsubscribe: http://listserv.ActiveState.com/mailman/mysubs
