Hi Asankha,
Thanks a lot, I can see the problem that you have mentioned. I need to check
it from the .Net side, which sometimes generates these bad requests.

Thanks,
Sudhir

On Tue, Dec 9, 2008 at 4:48 PM, Sudhir Mongia <[EMAIL PROTECTED]>wrote:

> Hi Asankha,
> Thanks for the quick reply. Let me go back and check what you are
> saying.will get back to you soon.
>
> Thanks,
> Sudhir
>
>
>
>
> On Tue, Dec 9, 2008 at 4:42 PM, Asankha C. Perera <[EMAIL PROTECTED]>wrote:
>
>>  Hi Sudhir
>>
>> Error 1  :com.ctc.wstx.exc.WstxUnexpectedCharException: Unexpected
>> character '-' (code 45) in prolog; expected '&lt;'&#xd;
>>   at [row,col {unknown-source}]: [2,1]
>>
>>  Request
>> POST /wsabacus/services/wsabacus HTTP/1.1
>> User-Agent: Mozilla/4.0 (compatible; MSIE 6.0; MS Web Services Client
>> Protocol 2.0.50727.1433)
>> Content-Type: application/soap+xml; charset=utf-8;
>> action="urn:getCalculationStatus"
>> Host: 10.253.101.130:9999
>> Cookie: JSESSIONID=ABD43A765104D4ED3A0EFF61DAD68ED8
>> Content-Length: 1463
>> Expect: 100-continue
>>
>>  ----MIMEBoundary633643641416156381
>> content-id: <[EMAIL PROTECTED]>
>> content-type: application/xop+xml; charset=utf-8;
>> type="application/soap+xml; charset=utf-8"
>> content-transfer-encoding: binary
>>
>>  <soap:Envelope xmlns:xop="http://www.w3.org/2004/08/xop/include";
>> xmlns:soap="http://www.w3.org/2003/05/soap-envelope"; xmlns:xsi="
>> http://www.w3.org/2001/XMLSchema-instance"; xmlns:xsd="
>> http://www.w3.org/2001/XMLSchema"; xmlns:wsa="
>> http://schemas.xmlsoap.org/ws/2004/08/addressing"; xmlns:wsse="
>> http://docs.oasis-open.org/wss/2004/01/oasis-200401-wss-wssecurity-secext-1.0.xsd";
>> xmlns:wsu="
>> http://docs.oasis-open.org/wss/2004/01/oasis-200401-wss-wssecurity-utility-1.0.xsd";><env:Header
>> xmlns:env="http://www.w3.org/2003/05/soap-envelope
>> "><wsa:Action>urn:getCalculationStatus</wsa:Action><wsa:MessageID>urn:uuid:bf39e47c-c561-4e7c-b7db-bc47980381db</wsa:MessageID><wsa:ReplyTo><wsa:Address>
>> http://schemas.xmlsoap.org/ws/2004/08/addressing/role/anonymous
>> </wsa:Address></wsa:ReplyTo><wsa:To>
>> http://10.253.101.130:9999/wsabacus/services/wsabacus</wsa:To><wsse:Security><wsu:Timestamp
>> wsu:Id="Timestamp-565f869f-fdd6-40ef-a2fe-a716685f44b2"><wsu:Created>2008-12-08T14:45:41Z</wsu:Created><wsu:Expires>2008-12-08T14:50:41Z</wsu:Expires></wsu:Timestamp></wsse:Security></env:Header><soap:Body><getCalculationStatus
>> xmlns="http://wsabacus/xsd
>> "><param0>087ed846</param0></getCalculationStatus></soap:Body></soap:Envelope>
>> ----MIMEBoundary633643641416156381--
>>
>> This request is invalid. See http://www.w3.org/TR/SOAP-attachmentsSection #5 
>> - Http Binding for a sample. The backend is expecting the mime
>> boundary in the content type. Since it doesn't find it, it thinks the
>> request is XML and tries to parse, and hits the first "-" of the payload
>> (i.e. ----MIME...part) and complains of this character
>>
>>  <soapenv:Reason><soapenv:Text
>> xml:lang="en-US">com.ctc.wstx.exc.WstxUnexpectedCharException: Unexpected
>> character '-' (code 45) in prolog; expected '&lt;'&#xd;
>>  at [row,col {unknown-source}]:
>> [2,1]</soapenv:Text></soapenv:Reason><soapenv:Detail /></soapenv:Fault>
>>
>>
>>   Error 2: Mime parts not found. Stream ended while searching for the
>> boundary
>>
>>
>>  ----MIMEBoundary633643641375692552--
>> POST /wsabacus/services/wsabacus HTTP/1.1
>> User-Agent: Mozilla/4.0 (compatible; MSIE 6.0; MS Web Services Client
>> Protocol 2.0.50727.1433)
>> Host: 10.253.101.130:9999
>> Cookie: JSESSIONID=ABD43A765104D4ED3A0EFF61DAD68ED8
>> Content-Type: multipart/related; type="application/xop+xml";
>> boundary=--MIMEBoundary633643641416156381; start="<
>> [EMAIL PROTECTED]>"; start-info="application/soap+xml;
>> charset=utf-8"
>> Content-Length: 1462
>> Expect: 100-continue
>>
>>
>>  ----MIMEBoundary633643641818451206
>> content-id: <[EMAIL PROTECTED]>
>> content-type: application/xop+xml; charset=utf-8;
>> type="application/soap+xml; charset=utf-8"
>> content-transfer-encoding: binary
>>
>>  <soap:Envelope xmlns:xop="http://www.w3.org/2004/08/xop/include";
>> xmlns:soap="http://www.w3.org/2003/05/soap-envelope"; xmlns:xsi="
>> http://www.w3.org/2001/XMLSchema-instance"; xmlns:xsd="
>> http://www.w3.org/2001/XMLSchema"; xmlns:wsa="
>> http://schemas.xmlsoap.org/ws/2004/08/addressing"; xmlns:wsse="
>> http://docs.oasis-open.org/wss/2004/01/oasis-200401-wss-wssecurity-secext-1.0.xsd";
>> xmlns:wsu="
>> http://docs.oasis-open.org/wss/2004/01/oasis-200401-wss-wssecurity-utility-1.0.xsd";><env:Header
>> xmlns:env="http://www.w3.org/2003/05/soap-envelope
>> "><wsa:Action>urn:deleteDataset</wsa:Action><wsa:MessageID>urn:uuid:25605344-dae6-4777-b493-77e650eae14f</wsa:MessageID><wsa:ReplyTo><wsa:Address>
>> http://schemas.xmlsoap.org/ws/2004/08/addressing/role/anonymous
>> </wsa:Address></wsa:ReplyTo><wsa:To>
>> http://10.253.101.130:9999/wsabacus/services/wsabacus</wsa:To><wsse:Security><wsu:Timestamp
>> wsu:Id="Timestamp-c155c096-4465-47f0-ad44-86054a9189fd"><wsu:Created>2008-12-08T14:46:21Z</wsu:Created><wsu:Expires>2008-12-08T14:51:21Z</wsu:Expires></wsu:Timestamp></wsse:Security></env:Header><soap:Body><deleteDataset
>> xmlns="http://wsabacus/xsd
>> "><param0>Q20_20081208_194107_CoBankv3</param0></deleteDataset></soap:Body></soap:Envelope>
>> ----MIMEBoundary633643641818451206--
>>
>> The content type in this one states the boundary as "
>> --MIMEBoundary633643641416156381" but this is not found on the payload;
>> which contains "----MIMEBoundary633643641818451206"
>>
>> cheers
>> asankha
>>
>> --
>> Asankha C. Pererahttp://adroitlogic.org
>> http://esbmagic.blogspot.com
>>
>>
>

Reply via email to