This does not look like a bug so I write about it here:
do-http-request (make-http-client-request actually) accepts net.uri or string as URI parameter. If it is a string, it is converted to net.uri object and everything works fine.
The problem I stumbled upon is as follows: do-http-request returns whatever it was passed as URI parameter if there are no redirects; but if there are, net.uri object is returned.
So, if I pass a string to do-http-request, I get string back if there are no redirects and net.uri object, if there are.
I think that do-http-request should always return net.uri object. What do you think?
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
This is a good idea. I'll look into it. I haven't uploaded a new version of AllegroServe is a while and it
is about time that I do so as I've made a few fixes and enhancements. I'll see if I can get this change into
the next uploaded version.
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
Hello,
This does not look like a bug so I write about it here:
do-http-request (make-http-client-request actually) accepts net.uri or string as URI parameter. If it is a string, it is converted to net.uri object and everything works fine.
The problem I stumbled upon is as follows: do-http-request returns whatever it was passed as URI parameter if there are no redirects; but if there are, net.uri object is returned.
So, if I pass a string to do-http-request, I get string back if there are no redirects and net.uri object, if there are.
I think that do-http-request should always return net.uri object. What do you think?
This is a good idea. I'll look into it. I haven't uploaded a new version of AllegroServe is a while and it
is about time that I do so as I've made a few fixes and enhancements. I'll see if I can get this change into
the next uploaded version.