Skip to content

error handling on non-xml responses #21

Open
@rbro

Description

@rbro

First, thanks for a great library. I ran into an issue today where my SSRS server was returning a 503 http error code. When that happened, php-ssrs threw an exception "String could not be parsed as XML", but didn't include any detail such as the http response code or the raw response from the server.

Looking at the callCurl() method in NTLM.php, it looks like the code is always expecting a xml response when the http code is between 300 and 600, but in my case today, a 503 error was thrown without valid xml. Similarily, a 404 could be thrown without valid xml.

Could the error handling be updated to send the http code and raw response for cases like this?

Thanks for your help.

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions