Bug 42773 - WSDL error causes HTTP 500 Response

php.internals

nick loeve

18 years ago
Hello, I see that the bug was marked fixed in 5.2.5, and that a HTTP 500 response code is not automatically sent, but isn't the whole problem that attempting to load a WSDL that cannot be loaded should raise an exception and not fatal error? Is this discussion appropriate for this bug, or should I open another? Cheers
-- Nick Loeve

Alexey Zakhlestin

18 years ago
imho, exceptions are preferrable in a lot of php's functions… but core php programmers are usually against exceptions if it is not an error of object-constructor On 11/19/07, nick loeve <trickie@gmail.com> wrote: > Hello, > > I see that the bug was marked fixed in 5.2.5, and that a HTTP 500 > response code is not automatically sent, but isn't the whole problem > that attempting to load a WSDL that cannot be loaded should raise an > exception and not fatal error? > > Is this discussion appropriate for this bug, or should I open another? > > Cheers > > -- > Nick Loeve > > -- > PHP Internals - PHP Runtime Development Mailing List > To unsubscribe, visit: http://www.php.net/unsub.php > > -- Alexey Zakhlestin http://blog.milkfarmsoft.com/

nick loeve

18 years ago
On Nov 19, 2007 4:21 PM, Alexey Zakhlestin <indeyets@gmail.com> wrote: > imho, exceptions are preferrable in a lot of php's functions… > but core php programmers are usually against exceptions if it is not > an error of object-constructor > Well in this case the constructor to the SoapClient class specifically allows you to say you would like to use exceptions for SoapFaults. Is this not a SoapFault... ? > > On 11/19/07, nick loeve <trickie@gmail.com> wrote: > > Hello, > > > > I see that the bug was marked fixed in 5.2.5, and that a HTTP 500 > > response code is not automatically sent, but isn't the whole problem > > that attempting to load a WSDL that cannot be loaded should raise an > > exception and not fatal error? > > > > Is this discussion appropriate for this bug, or should I open another? > > > > Cheers > > > > -- > > Nick Loeve > > > > -- > > PHP Internals - PHP Runtime Development Mailing List > > To unsubscribe, visit: http://www.php.net/unsub.php > > > > > > > -- > Alexey Zakhlestin > http://blog.milkfarmsoft.com/ > -- Nick Loeve www.trickie.org

Lukas Kahwe Smith

18 years ago
On 19.11.2007, at 16:26, nick loeve wrote:
> On Nov 19, 2007 4:21 PM, Alexey Zakhlestin <indeyets@gmail.com> wrote: >> imho, exceptions are preferrable in a lot of php's functions… >> but core php programmers are usually against exceptions if it is not >> an error of object-constructor >> > > Well in this case the constructor to the SoapClient class specifically > allows you to say you would like to use exceptions for SoapFaults. Is > this not a SoapFault... ?
well its not a soap fault .. since that is something that the service should throw. the wsdl reading error occurs before you even talk to the soap service. that being said, i do agree that this should not be a fatal error. fopen() type hacks prevent the use of the wsdl cache and are inefficient for obvious reasons. regards, Lukas