Bug #86617 for REST-Client: responseHeader throws exception if never connected

Mon Jul 01 17:48:14 2013 business2008 [...] rodneybeede.com - Ticket created

Subject:

responseHeader throws exception if never connected

When calling in my code: print STDERR "Response Header:\t" . $restClient->responseHeader() . "\n"; I get the following exception: REST::Client exception: no header provided to responseHeader This occurs if I failed to make a connection. Because $restClient->responseCode() returns a 501 error number I cannot tell if the remote server returned the 501 or if it failed locally. For timeouts or other failures where the remote server was never contacted their should be a way to know without having to call $restClient->responseHeader() and try catch an exception. Perhaps the error code could be in the 1000 range for $restClient->responseCode() when the client never connected to the remote server? That is outside of what the HTTP spec currently defines or perhaps a negative number?

Mon Jul 01 18:08:29 2013 mcrawfor [...] cpan.org - Correspondence added

First issue: I think you might be misunderstanding the API. responseHeader is used to fetch a single header value - the name of that header is a mandatory argument. Calling it with no arguments will always fail. Second issue: If you want to see *why* you're getting a 500 error, try looking at the resource returned. This little script illustrates the troubles: http://sprunge.us/HFBT On Mon Jul 01 17:48:14 2013, rbeede wrote: Show quoted text

> When calling in my code: > > print STDERR "Response Header:\t" . $restClient->responseHeader() . > "\n"; > > I get the following exception: > > REST::Client exception: no header provided to responseHeader > > > This occurs if I failed to make a connection. Because $restClient-

> >responseCode() returns a 501 error number I cannot tell if the

> remote server returned the 501 or if it failed locally. > > For timeouts or other failures where the remote server was never > contacted their should be a way to know without having to call > $restClient->responseHeader() and try catch an exception. > > Perhaps the error code could be in the 1000 range for $restClient-

> >responseCode() when the client never connected to the remote

> server? That is outside of what the HTTP spec currently defines or > perhaps a negative number?

Mon Jul 01 18:08:30 2013 The RT System itself - Status changed from 'new' to 'open'

Mon Jul 01 18:08:30 2013 mcrawfor [...] cpan.org - Status changed from 'open' to 'rejected'

Mon Jul 01 18:08:30 2013 mcrawfor [...] cpan.org - Taken