|
RSS Feed - WebSphere MQ Support
|
RSS Feed - Message Broker Support
|
 |
|
Web Service returning 400 Bad Request to HTTPRequest node |
« View previous topic :: View next topic » |
Author |
Message
|
yonny |
Posted: Tue Sep 26, 2006 8:23 am Post subject: Web Service returning 400 Bad Request to HTTPRequest node |
|
|
 Apprentice
Joined: 08 Jul 2001 Posts: 49 Location: Santo Domingo
|
Please excuse me for double post this, I also post it in the mq list but only recieved one suggestion and it did not worked.
I am calling a web service using an HTTPRequest node, but I am only getting this output:
(The output is from a trace node connected to the Error terminal of the HTTPRequest node)
(0x01000000):HTTPRequestHeader = (
(0x03000000):Content-Length = '75'
(0x03000000):POST = 'ws/iconn.asmx'
(0x03000000):SOAPAction = '" http://Merit/IConn/WS/PerformRequest "' <http://merit/IConn/WS/PerformRequest%22%27>
(0x03000000):Content-Type = 'text/xml; charset=utf-8'
(0x03000000):Host = 'riesgoimg'
)
(0x01000000):HTTPResponseHeader = (
(0x03000000):X-Original-HTTP-Status-Line = 'HTTP/1.1 400 Bad Request' (0x03000000):X-Original-HTTP-Status-Code = 400
(0x03000000):Connection = 'close'
(0x03000000):Date = 'Fri, 22 Sep 2006 15:25:04 GMT'
(0x03000000):Server = 'Microsoft-IIS/6.0'
(0x03000000):X-Powered-By = 'ASP.NET'
(0x03000000):X-AspNet-Version = '2.0.50727'
(0x03000000):Cache-Control = 'private'
(0x03000000):Content-Length = '0'
)
)
I am using WBMB 5.0 with fix pack 4. My message flow is basically:
MQInput -> Compute1 -> HTTPRequest -> Trace -> Compute2 -> MQOutput
MQInput Properties:
Message Domain: XMLNS
Thank you,
Yonny
Compute1 - ESQL Code:
Code: |
SET OutputRoot.HTTPRequestHeader.POST = '/ws/iconn.asmx HTTP/1.0';
SET OutputRoot.HTTPRequestHeader.Host = 'riesgoimg';
SET OutputRoot.HTTPRequestHeader."Content-Type" = 'text/xml; charset="UTF-8"';
SET OutputRoot.HTTPRequestHeader.SOAPAction = '"http://Merit/IConn/WS/PerformRequest"';
SET OutputLocalEnvironment.Destination.HTTP.RequestURL = 'http://riesgoimg:423/ws/iconn.asmx"; |
|
|
Back to top |
|
 |
jefflowrey |
Posted: Tue Sep 26, 2006 9:00 am Post subject: |
|
|
Grand Poobah
Joined: 16 Oct 2002 Posts: 19981
|
I can't necessarily speak to the validity of your code - but you should probably see if the application that's supposed to be receiving your request can give you more info about what's wrong with the request you're sending.
Maybe you're sending a valid HTTP request that the reciever doesn't like the content of. _________________ I am *not* the model of the modern major general. |
|
Back to top |
|
 |
youssef |
Posted: Wed Sep 27, 2006 12:35 am Post subject: |
|
|
Novice
Joined: 09 Sep 2006 Posts: 12
|
you might also try any ws client to send a valid request and them compare it with the one that the broker sent. I used this approach and could indetifiy some header param that I wasn't setting in my node. _________________ Regards,
Youssef |
|
Back to top |
|
 |
yonny |
Posted: Thu Sep 28, 2006 2:20 pm Post subject: |
|
|
 Apprentice
Joined: 08 Jul 2001 Posts: 49 Location: Santo Domingo
|
I am trying your suggestions, thank you. |
|
Back to top |
|
 |
|
|
 |
|
Page 1 of 1 |
|
You cannot post new topics in this forum You cannot reply to topics in this forum You cannot edit your posts in this forum You cannot delete your posts in this forum You cannot vote in polls in this forum
|
|
|
|