wso2是多部分/表單數據發佈請求的網關轉發

我正在使用一個演示API，它接收文件和註釋作爲multipart/form-data輸入並顯示文件和註釋的內容。以下是一個正確運行API的示例HTML：wso2是多部分/表單數據發佈請求的網關轉發

<html> 
    <body> 
    <FORM action="http://cgi-lib.berkeley.edu/ex/fup.cgi" method="post"> 
     <P>Choose file: <INPUT type="file" name="upfile"> 
     <p>Note: <INPUT type="text" name="note"> 
     <p><INPUT type="submit" value="Send"> 
    </FORM> 
    </body> 
</html>

現在我試圖在WSO2 APIM發佈者中創建託管API。下面是我填寫的參數：

我代替HTML的作用要經過我加了API：

<FORM action="http://ec2-52-48-93-41.eu-west-1.compute.amazonaws.com:8280/test" method="post">

但現在當我運行HTML我得到從API以下錯誤：

cgi-lib.pl: Unknown Content-type: application/x-www-form-urlencoded; charset=UTF-8

好像WSO2網關轉發該請求爲application/X WWW的窗體-urlencoded而非mulipart/form-data的。基於下面的討論multipart form data file upload using WSO2 API manger ?我試着用

<messageFormatter contentType="multipart/form-data" 
    class="org.wso2.carbon.relay.ExpandingMessageFormatter"/> 
<messageBuilder contentType="multipart/form-data" 
    class="org.wso2.carbon.relay.BinaryRelayBuilder"/>

註釋掉

<messageFormatter contentType="multipart/form-data" 
     class="org.apache.axis2.transport.http.MultipartFormDataFormatter"/> 
    <messageBuilder contentType="multipart/form-data" 
     class="org.apache.axis2.builder.MultipartFormDataBuilder"/>

並替換它們

然後重新啓動服務器，但它並不會造成任何影響。

任何想法將不勝感激。

我收集的一些日誌消息。目標API是不同的，但它也是一個multipart/form-data API，它可以轉儲任何它所接收的內容。

傳入的請求確實有內容類型的multipart/form-data的，具有292

DEBUG {org.apache.synapse.transport.http.headers} - http-incoming-1 >> POST /test/1.0.0 HTTP/1.1 {org.apache.synapse.transport.http.headers} 
DEBUG {org.apache.synapse.transport.http.headers} - http-incoming-1 >> Host: ec2-52-48-93-41.eu-west-1.compute.amazonaws.com:8280 {org.apache.synapse.transport.http.headers} 
DEBUG {org.apache.synapse.transport.http.headers} - http-incoming-1 >> Connection: keep-alive {org.apache.synapse.transport.http.headers} 
DEBUG {org.apache.synapse.transport.http.headers} - http-incoming-1 >> Content-Length: 292 {org.apache.synapse.transport.http.headers} 
DEBUG {org.apache.synapse.transport.http.headers} - http-incoming-1 >> Cache-Control: max-age=0 {org.apache.synapse.transport.http.headers} 
DEBUG {org.apache.synapse.transport.http.headers} - http-incoming-1 >> Accept: text/html,application/xhtml+xml,application/xml;q=0.9,image/webp,*/*;q=0.8 {org.apache.synapse.transport.http.headers} 
DEBUG {org.apache.synapse.transport.http.headers} - http-incoming-1 >> Origin: null {org.apache.synapse.transport.http.headers} 
DEBUG {org.apache.synapse.transport.http.headers} - http-incoming-1 >> Upgrade-Insecure-Requests: 1 {org.apache.synapse.transport.http.headers} 
DEBUG {org.apache.synapse.transport.http.headers} - http-incoming-1 >> User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/49.0.2623.87 Safari/537.36 {org.apache.synapse.transport.http.headers} 
DEBUG {org.apache.synapse.transport.http.headers} - http-incoming-1 >> Content-Type: multipart/form-data; boundary=----WebKitFormBoundaryqwBdAwOnlDYeHNNR {org.apache.synapse.transport.http.headers} 
DEBUG {org.apache.synapse.transport.http.headers} - http-incoming-1 >> Accept-Encoding: gzip, deflate {org.apache.synapse.transport.http.headers} 
DEBUG {org.apache.synapse.transport.http.headers} - http-incoming-1 >> Accept-Language: en-US,en;q=0.8,he;q=0.6 {org.apache.synapse.transport.http.headers} 
DEBUG {org.apache.synapse.transport.http.headers} - http-incoming-1 >> Cookie: region3_registry_menu=visible; region1_manage_menu=visible; region1_identity_menu=visible; menuPanel=visible; menuPanelType=main; csrftoken=n1g69f3slt1d90qvtaa28rtm1b {org.apache.synapse.transport.http.headers}

的呼出請求不具有內容類型內容長度：

DEBUG {org.apache.synapse.transport.http.headers} - http-outgoing-1 >> POST /sample2/api/company/upload HTTP/1.1 {org.apache.synapse.transport.http.headers} 
DEBUG {org.apache.synapse.transport.http.headers} - http-outgoing-1 >> Cookie: region3_registry_menu=visible; region1_manage_menu=visible; region1_identity_menu=visible; menuPanel=visible; menuPanelType=main; csrftoken=n1g69f3slt1d90qvtaa28rtm1b {org.apache.synapse.transport.http.headers} 
DEBUG {org.apache.synapse.transport.http.headers} - http-outgoing-1 >> Origin: null {org.apache.synapse.transport.http.headers} 
DEBUG {org.apache.synapse.transport.http.headers} - http-outgoing-1 >> Accept: text/html,application/xhtml+xml,application/xml;q=0.9,image/webp,*/*;q=0.8 {org.apache.synapse.transport.http.headers} 
DEBUG {org.apache.synapse.transport.http.headers} - http-outgoing-1 >> Cache-Control: max-age=0 {org.apache.synapse.transport.http.headers} 
DEBUG {org.apache.synapse.transport.http.headers} - http-outgoing-1 >> Upgrade-Insecure-Requests: 1 {org.apache.synapse.transport.http.headers} 
DEBUG {org.apache.synapse.transport.http.headers} - http-outgoing-1 >> Accept-Encoding: gzip, deflate {org.apache.synapse.transport.http.headers} 
DEBUG {org.apache.synapse.transport.http.headers} - http-outgoing-1 >> Accept-Language: en-US,en;q=0.8,he;q=0.6 {org.apache.synapse.transport.http.headers} 
DEBUG {org.apache.synapse.transport.http.headers} - http-outgoing-1 >> Transfer-Encoding: chunked {org.apache.synapse.transport.http.headers} 
DEBUG {org.apache.synapse.transport.http.headers} - http-outgoing-1 >> Host: localhost:8080 {org.apache.synapse.transport.http.headers} 
DEBUG {org.apache.synapse.transport.http.headers} - http-outgoing-1 >> Connection: Keep-Alive {org.apache.synapse.transport.http.headers} 
DEBUG {org.apache.synapse.transport.http.headers} - http-outgoing-1 >> User-Agent: Synapse-PT-HttpComponents-NIO {org.apache.synapse.transport.http.headers}

自然地，傳入響應具有HTTP 415，不受支持的媒體：

DEBUG {org.apache.synapse.transport.http.headers} - http-outgoing-1 << HTTP/1.1 415 Unsupported Media Type {org.apache.synapse.transport.http.headers} 
DEBUG {org.apache.synapse.transport.http.headers} - http-outgoing-1 << Server: Apache-Coyote/1.1 {org.apache.synapse.transport.http.headers} 
DEBUG {org.apache.synapse.transport.http.headers} - http-outgoing-1 << Content-Length: 0 {org.apache.synapse.transport.http.headers} 
DEBUG {org.apache.synapse.transport.http.headers} - http-outgoing-1 << Date: Mon, 28 Mar 2016 13:53:05 GMT {org.apache.synapse.transport.http.headers} 
DEBUG {org.apache.synapse.transport.http.headers} - http-incoming-1 << HTTP/1.1 415 Unsupported Media Type {org.apache.synapse.transport.http.headers} 
DEBUG {org.apache.synapse.transport.http.headers} - http-incoming-1 << Access-Control-Allow-Origin: * {org.apache.synapse.transport.http.headers} 
DEBUG {org.apache.synapse.transport.http.headers} - http-incoming-1 << Access-Control-Allow-Methods: POST {org.apache.synapse.transport.http.headers} 
DEBUG {org.apache.synapse.transport.http.headers} - http-incoming-1 << Access-Control-Allow-Headers: authorization,Access-Control-Allow-Origin,Content-Type {org.apache.synapse.transport.http.headers} 
DEBUG {org.apache.synapse.transport.http.headers} - http-incoming-1 << Date: Mon, 28 Mar 2016 13:53:05 GMT {org.apache.synapse.transport.http.headers} 
DEBUG {org.apache.synapse.transport.http.headers} - http-incoming-1 << Transfer-Encoding: chunked {org.apache.synapse.transport.http.headers} 
DEBUG {org.apache.synapse.transport.http.headers} - http-incoming-1 << Connection: keep-alive {org.apache.synapse.transport.http.headers}

另外值得一提的是th該API電子突觸：

<?xml version="1.0" encoding="UTF-8"?> 
<api xmlns="http://ws.apache.org/ns/synapse" 
    name="admin--test" 
    context="/test/1.0.0" 
    version="1.0.0" 
    version-type="context"> 
    <resource methods="POST" url-mapping="/*" faultSequence="fault"> 
     <inSequence> 
     <filter source="$ctx:AM_KEY_TYPE" regex="PRODUCTION"> 
      <then> 
       <property name="api.ut.backendRequestTime" 
         expression="get-property('SYSTEM_TIME')"/> 
       <send> 
        <endpoint name="admin--test_APIproductionEndpoint_0"> 
        <http uri-template="http://localhost:8080/sample2/api/company/upload"/> 
        </endpoint> 
       </send> 
      </then> 
      <else> 
       <sequence key="_sandbox_key_error_"/> 
      </else> 
     </filter> 
     </inSequence> 
     <outSequence> 
     <class name="org.wso2.carbon.apimgt.usage.publisher.APIMgtResponseHandler"/> 
     <send/> 
     </outSequence> 
    </resource> 
    <handlers> 
     <handler class="org.wso2.carbon.apimgt.gateway.handlers.security.CORSRequestHandler"> 
     <property name="apiImplementationType" value="ENDPOINT"/> 
     </handler> 
     <handler class="org.wso2.carbon.apimgt.gateway.handlers.security.APIAuthenticationHandler"/> 
     <handler class="org.wso2.carbon.apimgt.gateway.handlers.throttling.APIThrottleHandler"> 
     <property name="policyKey" value="gov:/apimgt/applicationdata/tiers.xml"/> 
     <property name="policyKeyApplication" 
        value="gov:/apimgt/applicationdata/app-tiers.xml"/> 
     <property name="policyKey" value="gov:/apimgt/applicationdata/tiers.xml"/> 
     <property name="policyKeyApplication" 
        value="gov:/apimgt/applicationdata/app-tiers.xml"/> 
     <property name="id" value="A"/> 
     <property name="policyKeyResource" 
        value="gov:/apimgt/applicationdata/res-tiers.xml"/> 
     </handler> 
     <handler class="org.wso2.carbon.apimgt.usage.publisher.APIMgtUsageHandler"/> 
     <handler class="org.wso2.carbon.apimgt.usage.publisher.APIMgtGoogleAnalyticsTrackingHandler"> 
     <property name="configKey" value="gov:/apimgt/statistics/ga-config.xml"/> 
     </handler> 
     <handler class="org.wso2.carbon.apimgt.gateway.handlers.ext.APIManagerExtensionHandler"/> 
    </handlers> 
</api>

來源

2016-03-28 Ofer Lahav

只是強調Ajanthan答案，爲了正確地保護頭部，正確的改變將是以下內容添加到passthru-http.properties

http.headers.preserve=Content-Length,Content-Type

這是ESB 4.9.0的新功能，所以沒有太多的文件記錄，但你可以在這個博客中閱讀：http://prabu-lk.blogspot.co.il/2015/09/how-to-preserving-http-headers-in-wso2.html

來源

2016-03-30 07:54:12

默認情況下，它看起來像新的API Manager會從clients.You沒有保護者某些標題需要添加以下屬性http.headers.preserve =在Content-Type庫/ conf目錄/passthru-http.properties以保留Content-Type標頭。

來源

2016-03-29 18:13:08 ajanthan

這是正確的。我補充說：http.headers。preserve = Content-Length，Content-Type來保存類型和長度（一些服務器依賴於它），現在它可以工作。 –

wso2是多部分/表單數據發佈請求的網關轉發

回答

相關問題