On Wed, 19 Aug 2015, Michael König wrote:
I'm generally a bit cautious about adding work-around for specific server
flaws unless they're in really wide use. Do you know anything about what
software/version this particular server is or how commonly it is used?
We sold around 1.3 million routers/APs total until this day. I cannot say
how many of those are in use. The behaviour of the TFTP implementation was
fixed recently. Before that all devices were affected.
That's... quite a lot of devices! =)
My change is still fully within the scope of the TFTP RFC. It just dumbs the
libcurl implementation of TFTP down to the state of RFC 1350 without the
TFTP options, when CURLOPT_TFTP_NO_OPTIONS is set.
If you think you can get something like that written into the documentation
for this new option as well, my objections are squashed and I'll even help
writing up a test case for it. =)
--
/ daniel.haxx.se
-------------------------------------------------------------------
List admin: http://cool.haxx.se/list/listinfo/curl-library
Etiquette: http://curl.haxx.se/mail/etiquette.html
