In rest_client module versions 2.2.2 (?) and before this worked like a
charm. When the web server returned a 404 or another error, the script
would log the error and go on. When rest_get() received a 200 OK, magic
Since we upgraded to rest_client module version 2.2.3 this morning this
behavior changed. When the server returns a 404, rest_get doesn't error
out, but goes on as before, and my script now tries to do magic on a 404
message's HTML body. Which is not what I want...
Did I use the rest_get() return values incorrectly, or is it a bug?
Re: rest_client behavior change in module version 2.2.3?
Although we saw it as a bugfix (404 response is not a transfer error!),
I will add a mention regarding this patch in the migration page. Maybe
it will help avoid more issues similar to yours remaining undetected
after upgrading to 2.2.3.
On 07.03.2017 14:51, Andreas Sikkema wrote:
> I did make the code a little more robust by not only checking if the
> rest_get() call succeeded, but also checking if $var(rcode) equalled
> "200" before doing the magic. This solved my problem.