I've a large F5 LTM load balancer environment I'm looking after which we are configuring to rate limit requests at a URI level. For human web users we are 302ing them to a busy page, but we also run web services and need to politely tell the soap client to go forth and procreate as well. Not knowing a whole heap about SOAP/XML responses I'm not clear on what we should tell the client. Will a very basic 500 reponse suffice or do we need to craft an legit SOAP response as well?
closed as off topic by grawity, BBlake, Ƭᴇcʜιᴇ007, Daniel Beck♦, Sathya♦ Jan 13 '12 at 12:23
Questions on Super User are expected to relate to computer software or computer hardware within the scope defined by the community. Consider editing the question or leaving comments for improvement if you believe the question can be reworded to fit within the scope. Read more about reopening questions here. If this question can be reworded to fit the rules in the help center, please edit the question.
The SOAP response is determined by the service definition (i.e. WSDL) outside that it is common to use appropriate HTTP response codes for circumstances outside the "contract".
Rather than being lazy and using 500, I'd choose from:
Review the full list and choose the most appropriate.
If the server is capable of returning an XML document detailing the error then it is normal to do so. The SOAP Services I use have this allowed for in the service definitions.
The client has to be able to cope with unadorned HTTP errors as sometimes a server fault occurs before the request XML is even parsed.