Re: [reSIProcate-users] FW: Support for quotes around boundary parameter

["Scott Godin" <slgodin@xxxxxxxxxxxx>]

Title: Support for quotes around boundary parameter

> Using reciprocate stack when we try to get boundary parameter which is enclosed in quotes we do not get the quotes.

 

I’m trying to understand why that is a problem.  Resiprocate can parse the boundary header if it is quoted or not.  If you ask for the boundary msg->header(h_ContentType).param(p_boundary) it will always return the value to you as unquoted.  The body itself should always contain the boundary as unquoted.

 

Scott

 

From: resiprocate-users-bounces@xxxxxxxxxxxxxxxxxxxx [mailto:resiprocate-users-bounces@xxxxxxxxxxxxxxxxxxxx] On Behalf Of Mohammed Sameer Momin
Sent: Friday, September 07, 2007 1:56 AM
To: resiprocate-users@xxxxxxxxxxxxxxxxxxxx
Subject: [reSIProcate-users] FW: Support for quotes around boundary parameter

 

 

Hi,

Resiprocate stack seems to have problem while parsing messages having content type as multipart/mixed with boundary parameter having colon in it and parameter enclosed in quotes. As per RFC

This is what RFC 2046 says:

   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. Implementors should be sure to
   study the grammar carefully in order to avoid producing invalid
   Content-type fields.  Thus, a typical "multipart" Content-Type header
   field might look like this:

     Content-Type: multipart/mixed; boundary=gc0p4Jq0M2Yt08j34c0p

   But the following is not valid:

     Content-Type: multipart/mixed; boundary=gc0pJq0M:08jU534c0p

   (because of the colon) and must instead be represented as

     Content-Type: multipart/mixed; boundary="gc0pJq0M:08jU534c0p"

 

Using reciprocate stack when we try to get boundary parameter which is enclosed in quotes we do not get the quotes.

 

Regards

Sameer