| |
|
RSS Feed - WebSphere MQ Support
|
RSS Feed - Message Broker Support
|
  |
|
| Dynamic assignment of Web Service URL |
« View previous topic :: View next topic » |
| Author |
Message
|
| ggriffith |
 Posted: Thu Aug 28, 2008 5:28 am Post subject: Dynamic assignment of Web Service URL |
 |
|
Acolyte
Joined: 17 Oct 2007
Posts: 67
|
I'm trying to set the url by setting either
OutputLocalEnvironment.Destination.HTTP.RequestURL
or
OutputRoot.HTTPRequestHeader."X-Original-HTTP-URL"
to the required address, but I keep getting the following error
(0x01000000):HTTPResponseHeader = (
(0x03000000):X-Original-HTTP-Status-Line = 'HTTP/1.1 505 HTTP Version Not Supported'
(0x03000000):X-Original-HTTP-Status-Code = 505
(0x03000000):Date = 'Thu, 28 Aug 2008 13:28:45 GMT'
(0x03000000):Server = 'Apache-Coyote/1.1'
(0x03000000):Connection = 'close'
It works perfectly when I set the HTTPRequest node property to the same value.
Any ideas |
|
| Back to top |
|
 |
| paranoid221 |
| Posted: Fri Aug 29, 2008 12:43 pm Post subject: |
|
|
Centurion
Joined: 03 Apr 2006
Posts: 101
Location: USA
|
When you set the URL property on the node properties, are you also setting the HTTP version to HTTP1.1?. By default, HTTP1.0 is pre-populated for that property and if you have not changed it 1.1, HTTP1.0 is what takes effect which explains why it was working. When you have used ESQL to code the URL though somehow HTTP1.1 is kicking in which is probably not supported by the service you are calling? Can't think of anything else going wrong at this time !!  I'll dig through if I can think of anything else.
_________________
LIFE is a series of complex calculations, somewhere multiplied by ZERO. |
|
| Back to top |
|
|
| ggriffith |
| Posted: Mon Sep 01, 2008 4:36 am Post subject: |
|
|
Acolyte
Joined: 17 Oct 2007
Posts: 67
|
| I have not changed the version property of the HTTPRequest node from the default setting of 1.0. |
|
| Back to top |
|
|
| ggriffith |
| Posted: Mon Sep 01, 2008 5:34 am Post subject: |
|
|
Acolyte
Joined: 17 Oct 2007
Posts: 67
|
Problem sorted  .
HTTPRequestHeader must follow the message properties, and before the message body. |
|
| Back to top |
|
|
| AkankshA |
| Posted: Mon Sep 01, 2008 8:08 pm Post subject: |
|
|
Grand Master
Joined: 12 Jan 2006
Posts: 1494
Location: Singapore
|
as a matter of fact its not just the HTTP header but for all transport specfic headers(MQ , JMS etc) .. they should always be after the properties header and before the payload.
_________________
Cheers |
|
| 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
|
|
|
|
