axis-java-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Vincent Dou (JIRA)" <j...@apache.org>
Subject [jira] Updated: (AXIS2-3906) CLONE -HTTP transport Attachments requests contains incorrect *boundary* header for "content-lenght" encoding method
Date Mon, 14 Jul 2008 02:41:31 GMT

     [ https://issues.apache.org/jira/browse/AXIS2-3906?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]

Vincent Dou updated AXIS2-3906:
-------------------------------

          Description: 
While generating SOAP with attachments message using Operation Client API, it generates one
*boundary* header in Content-Type (there is no issue for chunked): 
multipart/related whereas it generate all new header for SOAP Body section and attachment
section. See the relevant section from message below:
---------------------------------------------------------------------------------------------------
Content-Type: multipart/related; boundary=MIMEBoundaryurn:uuid:F02ECC18873CFB73E211412748909307;
type="application/xop+xml"; start="<0.urn:uuid:F02ECC18873CFB73E211412748909308@apache.org>";
start-info="text/xml"; charset=UTF-16
User-Agent: Axis2
Host: 127.0.0.1:8081
Proxy-Connection: Keep-Alive
Content-Length: 6956
---------------------------------------------------------------------------------------------------
--MIMEBoundaryurn_uuid_D57945993FC51941A31171314318273                <---------different
than one defined above
content-type: text/xml; charset=UTF-8
content-transfer-encoding: 8bit
content-id: <0.urn:uuid:D57945993FC51941A31171314318290@apache.org>
---------------------------------------------------------------------------------------------------
--MIMEBoundaryurn_uuid_D57945993FC51941A31171314318273               <---------different
than one defined above
content-type: text/xml
content-transfer-encoding: binary
content-id: <urn:uuid:D57945993FC51941A31171314318022>
---------------------------------------------------------------------------------------------------


  was:
While generating SOAP with attachments message using Operation Client API, it generates one
*boundary* header in Content-Type: 
multipart/related whereas it generate all new header for SOAP Body section and attachment
section. See the relevant section from message below:
---------------------------------------------------------------------------------------------------
Content-Type: multipart/related; boundary=MIMEBoundaryurn:uuid:F02ECC18873CFB73E211412748909307;
type="application/xop+xml"; start="<0.urn:uuid:F02ECC18873CFB73E211412748909308@apache.org>";
start-info="text/xml"; charset=UTF-16
User-Agent: Axis2
Host: 127.0.0.1:8081
Proxy-Connection: Keep-Alive
Content-Length: 6956
---------------------------------------------------------------------------------------------------
--MIMEBoundaryurn_uuid_D57945993FC51941A31171314318273                <---------different
than one defined above
content-type: text/xml; charset=UTF-8
content-transfer-encoding: 8bit
content-id: <0.urn:uuid:D57945993FC51941A31171314318290@apache.org>
---------------------------------------------------------------------------------------------------
--MIMEBoundaryurn_uuid_D57945993FC51941A31171314318273               <---------different
than one defined above
content-type: text/xml
content-transfer-encoding: binary
content-id: <urn:uuid:D57945993FC51941A31171314318022>
---------------------------------------------------------------------------------------------------


    Affects Version/s: 1.4
                       1.3
                       1.2

> CLONE -HTTP transport Attachments requests contains incorrect *boundary* header for "content-lenght"
encoding method
> --------------------------------------------------------------------------------------------------------------------
>
>                 Key: AXIS2-3906
>                 URL: https://issues.apache.org/jira/browse/AXIS2-3906
>             Project: Axis 2.0 (Axis2)
>          Issue Type: Bug
>          Components: transports
>    Affects Versions: 1.4, 1.3, 1.2, 1.1.1
>         Environment: Java 5, Win XP, Eclipse 3.1
>            Reporter: Vincent Dou
>            Assignee: Thilina Gunarathne
>            Priority: Blocker
>
> While generating SOAP with attachments message using Operation Client API, it generates
one *boundary* header in Content-Type (there is no issue for chunked): 
> multipart/related whereas it generate all new header for SOAP Body section and attachment
section. See the relevant section from message below:
> ---------------------------------------------------------------------------------------------------
> Content-Type: multipart/related; boundary=MIMEBoundaryurn:uuid:F02ECC18873CFB73E211412748909307;
type="application/xop+xml"; start="<0.urn:uuid:F02ECC18873CFB73E211412748909308@apache.org>";
start-info="text/xml"; charset=UTF-16
> User-Agent: Axis2
> Host: 127.0.0.1:8081
> Proxy-Connection: Keep-Alive
> Content-Length: 6956
> ---------------------------------------------------------------------------------------------------
> --MIMEBoundaryurn_uuid_D57945993FC51941A31171314318273                <---------different
than one defined above
> content-type: text/xml; charset=UTF-8
> content-transfer-encoding: 8bit
> content-id: <0.urn:uuid:D57945993FC51941A31171314318290@apache.org>
> ---------------------------------------------------------------------------------------------------
> --MIMEBoundaryurn_uuid_D57945993FC51941A31171314318273               <---------different
than one defined above
> content-type: text/xml
> content-transfer-encoding: binary
> content-id: <urn:uuid:D57945993FC51941A31171314318022>
> ---------------------------------------------------------------------------------------------------

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.


---------------------------------------------------------------------
To unsubscribe, e-mail: axis-dev-unsubscribe@ws.apache.org
For additional commands, e-mail: axis-dev-help@ws.apache.org


Mime
View raw message