Well if it’s really unfixable then we deprecate the old broken API and add a new API that’s not broken. If this is a recent regression then there may be apps both ways.
From: Gregg Reynolds [mailto:[email protected]] Sent: Thursday, January 25, 2018 2:55 PM To: Dave Thaler <[email protected]> Cc: [email protected]; [email protected]; iotivity-dev <[email protected]> Subject: Re: [dev] percent encoding IPv6 endpoints On Thu, Jan 25, 2018 at 4:48 PM, Dave Thaler <[email protected]<mailto:[email protected]>> wrote: Ok, after groveling through a bunch of code to refresh my memory, eps->addr should be an IP literal string, not a URL authority component string. So yes it is a bug and the “%25” should be “%” in OCMapZoneIdToLinkLocalEndpoint. Alas, since this is released into the wild, I'm not sure how to fix it. Change that code to use "%" instead of "%25"and you risk breaking app code that is hard-coded to depend on "%25". Since eps->addr is exposed (one way or another) to client code. Not to mention the C++ api, I have no idea how that works. G
_______________________________________________ iotivity-dev mailing list [email protected] https://lists.iotivity.org/mailman/listinfo/iotivity-dev
