HTTP 500 Status Codes
As mentioned earlier in the chapter, you will sometimes encounter HTTP 500 status codes. You encounter these errors when something about your request causes the entire request to fail. Typically, such erroneous conditions occur before the first item in the request is processed. For instance, if you pass in a request that is not schema-compliant, you receive an HTTP 500 status code, and the response code of ErrorSchemaValidation is embedded in the detail node of the SOAP fault. Let’s see that in action. The invalid request is shown in Example 18-12.
Example 18-12. Schema invalid request
<CreateItem xmlns=".../messages"
xmlns:t=".../types"
MessageDisposition="SaveOnly">
<Items>
<t:Messagez> <t:Subject>I am batched message #1</t:Subject> ...
Get Inside Microsoft® Exchange Server 2007 Web Services now with the O’Reilly learning platform.
O’Reilly members experience books, live events, courses curated by job role, and more from O’Reilly and nearly 200 top publishers.