You are viewing a plain text version of this content. The canonical link for it is here.
Posted to java-dev@axis.apache.org by "yogen (JIRA)" <ji...@apache.org> on 2007/02/12 23:43:05 UTC

[jira] Created: (AXIS2-2163) HTTP transport Attachments requests contains incorrect *boundary* header

HTTP transport Attachments requests contains incorrect *boundary* header
------------------------------------------------------------------------

                 Key: AXIS2-2163
                 URL: https://issues.apache.org/jira/browse/AXIS2-2163
             Project: Axis 2.0 (Axis2)
          Issue Type: Bug
          Components: transports
    Affects Versions: 1.1.1
         Environment: Java 5, Win XP, Eclipse 3.1
            Reporter: yogen
            Priority: Blocker


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....@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....@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


[jira] Commented: (AXIS2-2163) HTTP transport Attachments requests contains incorrect *boundary* header

Posted by "Deepal Jayasinghe (JIRA)" <ji...@apache.org>.
    [ https://issues.apache.org/jira/browse/AXIS2-2163?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12483410 ] 

Deepal Jayasinghe commented on AXIS2-2163:
------------------------------------------

Thilina , what is the status of this issue ?
do we need to keep this as a blocker ?

Thanks
Deepal

> HTTP transport Attachments requests contains incorrect *boundary* header
> ------------------------------------------------------------------------
>
>                 Key: AXIS2-2163
>                 URL: https://issues.apache.org/jira/browse/AXIS2-2163
>             Project: Axis 2.0 (Axis2)
>          Issue Type: Bug
>          Components: transports
>    Affects Versions: 1.1.1
>         Environment: Java 5, Win XP, Eclipse 3.1
>            Reporter: yogen
>         Assigned To: Thilina Gunarathne
>            Priority: Blocker
>
> 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....@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....@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


[jira] Commented: (AXIS2-2163) HTTP transport Attachments requests contains incorrect *boundary* header

Posted by "Thilina Gunarathne (JIRA)" <ji...@apache.org>.
    [ https://issues.apache.org/jira/browse/AXIS2-2163?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12477248 ] 

Thilina Gunarathne commented on AXIS2-2163:
-------------------------------------------

If possible please attach some resources (test case) to reproduce the bug..

> HTTP transport Attachments requests contains incorrect *boundary* header
> ------------------------------------------------------------------------
>
>                 Key: AXIS2-2163
>                 URL: https://issues.apache.org/jira/browse/AXIS2-2163
>             Project: Axis 2.0 (Axis2)
>          Issue Type: Bug
>          Components: transports
>    Affects Versions: 1.1.1
>         Environment: Java 5, Win XP, Eclipse 3.1
>            Reporter: yogen
>         Assigned To: Thilina Gunarathne
>            Priority: Blocker
>
> 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....@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....@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


[jira] Assigned: (AXIS2-2163) HTTP transport Attachments requests contains incorrect *boundary* header

Posted by "Deepal Jayasinghe (JIRA)" <ji...@apache.org>.
     [ https://issues.apache.org/jira/browse/AXIS2-2163?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Deepal Jayasinghe reassigned AXIS2-2163:
----------------------------------------

    Assignee: Thilina Gunarathne

> HTTP transport Attachments requests contains incorrect *boundary* header
> ------------------------------------------------------------------------
>
>                 Key: AXIS2-2163
>                 URL: https://issues.apache.org/jira/browse/AXIS2-2163
>             Project: Axis 2.0 (Axis2)
>          Issue Type: Bug
>          Components: transports
>    Affects Versions: 1.1.1
>         Environment: Java 5, Win XP, Eclipse 3.1
>            Reporter: yogen
>         Assigned To: Thilina Gunarathne
>            Priority: Blocker
>
> 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....@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....@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


[jira] Resolved: (AXIS2-2163) HTTP transport Attachments requests contains incorrect *boundary* header

Posted by "Thilina Gunarathne (JIRA)" <ji...@apache.org>.
     [ https://issues.apache.org/jira/browse/AXIS2-2163?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Thilina Gunarathne resolved AXIS2-2163.
---------------------------------------

    Resolution: Cannot Reproduce

A quick run of the latest Axis2 SwA sample gave me the following correct MIME package. Please reopen this if there is a way to reproduce the bug..


POST /axis2/services/SWASampleService HTTP/1.1

Content-Type: multipart/related; boundary=MIMEBoundaryurn_uuid_4EB9B465A116B0D4181174639911765; type="text/xml"; start="<0....@apache.org>"; charset=UTF-8

SOAPAction: "urn:uploadFile"

User-Agent: Axis2

Host: 127.0.0.1:8082

Transfer-Encoding: chunked



fea

--MIMEBoundaryurn_uuid_4EB9B465A116B0D4181174639911765

content-type: text/xml; charset=UTF-8

content-transfer-encoding: 8bit

content-id: <0....@apache.org>



<?xml version='1.0' encoding='UTF-8'?><soapenv:Envelope xmlns:soapenv="http://schemas.xmlsoap.org/soap/envelope/"><soapenv:Body><swa:uploadFile xmlns:swa="http://service.soapwithattachments.sample/xsd"><swa:name>/home/thilina/Desktop/temptalk1</swa:name><swa:attchmentID>urn:uuid:4EB9B465A116B0D4181174639911686</swa:attchmentID></swa:uploadFile></soapenv:Body></soapenv:Envelope>

--MIMEBoundaryurn_uuid_4EB9B465A116B0D4181174639911765

content-type: application/octet-stream

content-transfer-encoding: binary

content-id: <urn:uuid:4EB9B465A116B0D4181174639911686>


.............
3a



--MIMEBoundaryurn_uuid_4EB9B465A116B0D4181174639911765--

0




> HTTP transport Attachments requests contains incorrect *boundary* header
> ------------------------------------------------------------------------
>
>                 Key: AXIS2-2163
>                 URL: https://issues.apache.org/jira/browse/AXIS2-2163
>             Project: Axis 2.0 (Axis2)
>          Issue Type: Bug
>          Components: transports
>    Affects Versions: 1.1.1
>         Environment: Java 5, Win XP, Eclipse 3.1
>            Reporter: yogen
>         Assigned To: Thilina Gunarathne
>            Priority: Blocker
>
> 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....@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....@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


[jira] Commented: (AXIS2-2163) HTTP transport Attachments requests contains incorrect *boundary* header

Posted by "Vincent Dou (JIRA)" <ji...@apache.org>.
    [ https://issues.apache.org/jira/browse/AXIS2-2163?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12613224#action_12613224 ] 

Vincent Dou commented on AXIS2-2163:
------------------------------------


The samples you gave are different. 

The first one does exist the issue for "Content-Length" HTTP Encoding method.  There is no issue for "Chuncked" encoding method as you gave in the last example.

So , Please reopen this issue for "Content-Length".




> HTTP transport Attachments requests contains incorrect *boundary* header
> ------------------------------------------------------------------------
>
>                 Key: AXIS2-2163
>                 URL: https://issues.apache.org/jira/browse/AXIS2-2163
>             Project: Axis 2.0 (Axis2)
>          Issue Type: Bug
>          Components: transports
>    Affects Versions: 1.1.1
>         Environment: Java 5, Win XP, Eclipse 3.1
>            Reporter: yogen
>            Assignee: Thilina Gunarathne
>            Priority: Blocker
>
> 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....@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....@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