Re: SOAP binding to HTTP

You will be happy to know that SOAPAction is gone in SOAP 1.2[1].

Its function is to allow SOAP unaware processors (like
routers/firewalls) to identify soap traffic and as an option dispatch
mechanism for server toolkits.

In SOAP 1.2 a new content-type header value: application/soap+xml is
used to identify SOAP messages to transport layer devices.  And the
SOAPaction value can be provided in an option "action" parameter of the
media type.

Content-Type: application/soap+xml; charset="utf-8; action="the soap
action"



Jim Murphy
Mindreef, Inc.
http://www.mindreef.com

[1] - http://www.w3.org/TR/2002/CR-soap12-part0-20021219/ section 6


> -----Original Message-----
> From: Discussion of implementing SOAP applications today
> [mailto:[email protected]] On Behalf Of Dean, Michael D.
> Sent: Thursday, April 17, 2003 12:22 PM
> To: [email protected]
> Subject: [SOAP] SOAP binding to HTTP
> Importance: Low
>
>
> It seems to me that the binding between SOAP and HTTP is
> unnecessarily "coupled" due to the specification of a
> SOAP-specific HTTP Header (SOAP ACTION:)...wouldn't the ideal
> situation be that a particular value or value structure to an
> standard HTTP header would serve adequately?  What are the
> reasons for a SOAP-specific HTTP header?
>
> > Best Regards,
> >
> > Michael Dean
> > Sun Certified Programmer for the Java 2 Platform
> > Washington State Department of Corrections
> > 360-664-8802
> > mailto:[email protected]
> >
> >  "Instead of always harping on a man's faults,
> >          tell him of his virtues.
> >   Try to pull him out of his rut of bad habits."
> >                        - Pollyanna
> >
> >
>
>