HTTP Binding

• The most developed SOAP transport is HTTP.
  • The fact that most firewalls block everything but port 80 (HTTP) make it most practical.
• You can only use POST
• The requested URI indicates the resource to which the invocation is "posted".
• A sample message submission looks like:

POST /Charging HTTP/1.1
Host: travelcompany.example.org
Content-Type: application/soap; charset="utf-8"
Content-Length: nnnn

<?xml version='1.0' ?>
<env:Envelope xmlns:env="http://www.w3.org/2001/12/soap-envelope" >
  <env:Header>
    ::::::
  </env:Header> 
  <env:Body>
    <m:reserveAndCharge> 
      ::::::
    </m:reserveAndCharge>
  </env:Body>
</env:Envelope>

• The reply might look like:

HTTP/1.1 200 OK
Content-Type: application/soap; charset="utf-8"
Content-Length: nnnn

<?xml version='1.0' ?>
<env:Envelope xmlns:env="http://www.w3.org/2001/12/soap-envelope" >
  <env:Header>
    ::::
  </env:Header> 
  <env:Body>
    ::::
  </env:Body>
</env:Envelope>

• Unless an error occurs, in which case it might look like:

HTTP/1.1 500 Internal Server Error
Content-Type: text/xml; charset="utf-8"
Content-Length: nnnn

<?xml version='1.0' ?>
<env:Envelope xmlns:env="http://www.w3.org/2001/12/soap-envelope">
  <env:Body>
    <env:Fault>
      <faultcode>env:Receiver</faultcode>
      <faultstring>Processing Error</faultstring>
      <detail>
        <e:myfaultdetails xmlns:e="http://travelcompany.example.org/faults" >
          <message>Name does not match card number</message>
          <errorcode>999</errorcode>
        </e:myfaultdetails>
      </detail>
    </env:Fault>
  </env:Body>
</env:Envelope>