Editing SOAP (section)

==Transport methods==
Both [[SMTP]] and [[HTTP]] are valid application layer protocols used as transport for SOAP, but HTTP has gained wider acceptance as it works well with today's internet infrastructure; specifically, HTTP works well with network [[firewall (networking)|firewalls]]. SOAP may also be used over [[HTTPS]] (which is the same protocol as HTTP at the application level, but uses an [[Transport Layer Security|encrypted transport protocol]] underneath) with either simple or mutual authentication; this is the advocated [[WS-I]] method to provide web service security as stated in the [[WS-I Basic Profile]] 1.1.

This is a major advantage over other distributed protocols like [[General Inter-ORB Protocol|GIOP/IIOP]] or [[Distributed Component Object Model|DCOM]], which are normally filtered by firewalls. SOAP over [[AMQP]] is yet another possibility that some implementations support.  SOAP also has an advantage over [[Distributed Component Object Model|DCOM]] that it is unaffected by security rights configured on the machines that require knowledge of both transmitting and receiving nodes. This lets SOAP be loosely coupled in a way that is not possible with [[Distributed Component Object Model|DCOM]].  There is also the [[SOAP-over-UDP]] [[OASIS (organization)|OASIS]] standard.