ASG
IBM
Zystems
Cressida
Icon
Netflexity
 
  MQSeries.net
Search  Search       Tech Exchange      Education      Certifications      Library      Info Center      SupportPacs      LinkedIn  Search  Search                                                                   FAQ  FAQ   Usergroups  Usergroups
 
Register  ::  Log in Log in to check your private messages
 
RSS Feed - WebSphere MQ Support RSS Feed - Message Broker Support

MQSeries.net Forum Index » WebSphere Message Broker (ACE) Support » SOAPAction header in HTTPRequest node

Post new topic  Reply to topic
 SOAPAction header in HTTPRequest node « View previous topic :: View next topic » 
Author Message
damianharvey
PostPosted: Sun Nov 11, 2012 3:11 pm    Post subject: SOAPAction header in HTTPRequest node Reply with quote

Acolyte

Joined: 05 Aug 2003
Posts: 59
Location: Sydney, Australia

I'm sending some XML to PeopleSoft using the HTTPRequest node. Plain XML/RPC. It's adding a blank SOAPAction header (which is explained in the docs). Unfortunately this causes PeopleSoft to think that the whole message is SOAP.

Is there a good reason for this header to be automatically added? It seems strange and I can't think of any good reason for it to be there.

I realise that I can disable the automatic generation of headers, but this question is why is it there in the first place?

Thanks,

Damian.
Back to top
View user's profile Send private message
kash3338
PostPosted: Sun Nov 11, 2012 9:37 pm    Post subject: Re: SOAPAction header in HTTPRequest node Reply with quote

Shaman

Joined: 08 Feb 2009
Posts: 709
Location: Chennai, India

damianharvey wrote:
Is there a good reason for this header to be automatically added? It seems strange and I can't think of any good reason for it to be there.

I realise that I can disable the automatic generation of headers, but this question is why is it there in the first place?


This is what SOAP 1.1 specification says,

Quote:

The SOAPAction HTTP request header field can be used to indicate the intent of the SOAP HTTP request. The value is a URI identifying the intent. SOAP places no restrictions on the format or specificity of the URI or that it is resolvable. An HTTP client MUST use this header field when issuing a SOAP HTTP Request.

The presence and content of the SOAPAction header field can be used by servers such as firewalls to appropriately filter SOAP request messages in HTTP. The header field value of empty string ("") means that the intent of the SOAP message is provided by the HTTP Request-URI. No value means that there is no indication of the intent of the message.
Back to top
View user's profile Send private message Send e-mail
damianharvey
PostPosted: Sun Nov 11, 2012 9:53 pm    Post subject: Re: SOAPAction header in HTTPRequest node Reply with quote

Acolyte

Joined: 05 Aug 2003
Posts: 59
Location: Sydney, Australia

kash3338 wrote:
This is what SOAP 1.1 specification says...

Thanks but this doesn't answer my question. An HTTP request doesn't need to have anything to do with SOAP.
Back to top
View user's profile Send private message
Display posts from previous:   
Post new topic  Reply to topic Page 1 of 1

MQSeries.net Forum Index » WebSphere Message Broker (ACE) Support » SOAPAction header in HTTPRequest node
Jump to:  



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
Protected by Anti-Spam ACP
 
 


Theme by Dustin Baccetti
Powered by phpBB © 2001, 2002 phpBB Group

Copyright © MQSeries.net. All rights reserved.