ClientProtocolException : are you sure that you have the protocol, and more specifically the url including parameters, correct?
thus:
https://forum.mendix.com/link/questions/95290 instead of www.mxforum.mendix.com/link/questions/{1}
Four of our team are also attempting this learning path and running into the same error(s). Using Theo’s fix of hard coding the URI, I was able to make the error go away, but it’s still impossible to tell if the REST call actually works, because there’s a microflow that populated the Products table automatically if the database is empty, so all the records that are supposed to be fetched are already in the database.
The fact that the constant appears to be failing to deliver the URI string to the microflow suggests a breakdown between those two components. This is further supported by the fact that calling the REST API at that URI with POSTMan, Fiddler, Swagger and using a Python script all return the expected results. The only place it doesn’t work is in the app that you’re trying use it in. This could be a bug, or it could be just one more example of a learning path lesson path leaving out a crucial nugget of information that you wouldn’t know you need unless you already had it. Given the annoying frequency with which we encounter the latter case, that would be my guess. But I have no idea what that nugget might be.
Try using
http://localhost:8079/rest/restproducts/v1/product
instead of
http://localhost:8079/rest-doc/rest/restproducts/v1/