Sign Up to our social questions and Answers Engine to ask questions, answer people’s questions, and connect with other people.
Login to our social questions & Answers Engine to ask questions answer people’s questions & connect with other people.
Lost your password? Please enter your email address. You will receive a link and will create a new password via email.
Please briefly explain why you feel this question should be reported.
Please briefly explain why you feel this answer should be reported.
Please briefly explain why you feel this user should be reported.
I’m currently writing a PHP script that 3rd party clients will be able to access using GET. It will take a few GET parameters and return an XML document with results.
My question is, if required GET parameters are left out or contain invalid data how should display errors back to the end user?
Should I return a completely different XML document with the error details or the same XML document with errors in the existing fields or just put the errors as HTML?
How is the content requested? Do some users surf to the page? Or is another PHP script requesting those details? If it’s a PHP script requesting the XML, I would just output HTTP 400 Bad Request. If it’s a human being browsing to the site, I think a friendly error page would be fine if the parameters are crucial.
For example, if they are requesting for
but they did not supply the file parameter, you would simply tell them that there was an error, no file was specified.