Hi, "MAX_URI_LENGH (256)" has been patched in the Iotivity master branch, but not applied in the release branch which had been forked before change happened. Fix is required in the 1.1-REL branch.
BR, Uze Choi -----Original Message----- From: cftg at openconnectivity.org [mailto:[email protected]] On Behalf Of Mitch Kettrick Sent: Saturday, May 28, 2016 7:33 AM To: 'Mats Wichmann'; 'OCF Core Framework Task Group' Subject: RE: [cftg] lengths of things in spec vs IoTivity Hi, To date, we have not been testing maximum allowable lengths with the CTT other than to ensure that values returned meet the requirements. When testing Servers, there really aren?t many ways to test these things since the Server defines the length of things in most cases. Once we start doing CREATE, we'll be able to better validate proper behavior by trying to add a new Resource to a Collection with a really long URI, for example. However, for testing Clients, it's possible for the CTT to set the URI length of a Resource of up to 256 bytes per Table 1. What will an IoTivity Client do when faced with this situation? I think we should address this now to ensure that nothing breaks in the future. Mitch -----Original Message----- From: cftg at openconnectivity.org [mailto:[email protected]] On Behalf Of Mats Wichmann Sent: Friday, May 27, 2016 12:36 PM To: OCF Core Framework Task Group Subject: [cftg] lengths of things in spec vs IoTivity It looks to me like we're mismatched on some of the lengths. We've fiddled several times in the spec with what type we assign things, and what the resulting limits end up being. IoTivity code has this: /** * Maximum length of the URI supported by client/server while processing * REST requests/responses. */ #define MAX_URI_LENGTH (64) /** * Maximum length of the query supported by client/server while processing * REST requests/responses. */ #define MAX_QUERY_LENGTH (64) /** * Maximum length of the Manufacturer name supported by the server * for manufacturer name. */ #define MAX_MANUFACTURER_NAME_LENGTH (16) /** * Maximum length of the URL to the Manufacturer details supported by * the server. */ #define MAX_MANUFACTURER_URL_LENGTH (32) the URI length I believe (I was told, but not by a core developer) refers only to the path piece and excludes scheme, authority or query. ----- No virus found in this message. Checked by AVG - www.avg.com Version: 2016.0.7598 / Virus Database: 4568/12306 - Release Date: 05/27/16
