GET http request

Hi,

Thanks for your explanations and suggestions. To be sure where the bug is, I will create a small test application with curllib and with a hard coded http request. I will keep you informed of the result.

Regards

Bart

-----Oorspronkelijk bericht-----
Van: curl-library <curl-library-bounces_at_cool.haxx.se> Namens Erik Janssen via curl-library
Verzonden: dinsdag 8 september 2020 17:18
Aan: libcurl development <curl-library_at_cool.haxx.se>
CC: Erik Janssen <Erik.Janssen_at_axis.com>; Daniel Stenberg <daniel_at_haxx.se>
Onderwerp: [External] RE: FW: GET http request

>> I have simulated with the command line and indeed see a second
>> request in which the url is unchanged compared to the first request.
>> But why are we seeing the changed url in the WireShark?

> It shouldn't change, it's a bug. But a bug we've not heard of before which makes me suspect the origin of it isn't in libcurl. I could be > wrong of course.

> If it would be in libcurl, then surely the curl command line would also do it that way?

Hi Bart,

I would check how the URL you pass to libcurl is constructed. Something quirky may be there that was no problem before but now provokes a bug given libcurl changed implementation? Maybe enable verbose curl output in your own code to hopefully get a quick hint. But inspecting the code with the failure in mind can be quick too

I think many systems in the world work by accident.. likely you happened to build on something forgiving and now that's gone. I suppose many on this list have been there too. I was :)

Erik

-------------------------------------------------------------------
Unsubscribe: https://cool.haxx.se/list/listinfo/curl-library
Etiquette: https://curl.haxx.se/mail/etiquette.html

-------------------------------------------------------------------
Unsubscribe: https://cool.haxx.se/list/listinfo/curl-library
Etiquette: https://curl.haxx.se/mail/etiquette.html
Received on 2020-09-09