viewer.git/indra/llcommon/tests/lluri_test.cpp, branch cef_147 Megapahit's fork of the Second Life viewer. https://megapahit.org/viewer.git/atom?h=cef_147 2024-04-29T04:56:09Z #824 Process source files in bulk: replace tabs with spaces, convert CRLF to LF, and trim trailing whitespaces as needed 2024-04-29T04:56:09Z Andrey Lihatskiy alihatskiy@productengine.com 2024-04-29T04:43:28Z urn:sha1:1b68f71348ecf3983b76b40d7940da8377f049b7 SL-10954 Unit test escapePathAndData 2019-05-07T17:36:19Z andreykproductengine andreykproductengine@lindenlab.com 2019-05-07T17:36:19Z urn:sha1:098f6399fb00498e2866c63cb455c1a5d6700e76 remove execute permission from many files that should not have it 2015-11-10T14:48:56Z Oz Linden oz@lindenlab.com 2015-11-10T14:48:56Z urn:sha1:c8726aba303bcf1207b730a344536e25491420bc Update Mac and Windows breakpad builds to latest 2013-03-29T14:50:08Z Graham Madarasz graham@lindenlab.com 2013-03-29T14:50:08Z urn:sha1:bf6182daa8b4d7cea79310547f71d7a3155e17b0 Fix longstanding LLURI::buildHTTP() bug when passing string path. 2012-08-31T13:55:52Z Nat Goodspeed nat@lindenlab.com 2012-08-31T13:55:52Z urn:sha1:7db0cb7583b829be3b4884b69a31af1bbdfaadfb The LLURI::buildHTTP() overloads that take an LLSD 'path' accept 'undefined', LLSD::String and (LLSD::Array of LLSD::String). A sequence of path components passed in an Array is constructed into a slash-separated path. There are unit tests in lluri_test.cpp to exercise that case. To my amazement, there were NO unit tests covering the case of an LLSD::String path. The code for that case escaped and appended the entire passed string. While that might be fine for a 'path' consisting of a single undecorated path component, the available documentation does not forbid one from passing a path containing slashes as well. But this had the dubious effect of replacing every slash with %2F. In particular, decomposing a URL string with one LLURI instance and constructing another like it using LLURI::buildHTTP() was not symmetrical. Having consulted with Richard, I made the string-path logic a bit more nuanced: - The passed path string is split on slashes. Every path component is individually escaped, then recombined with slashes into the final path. - Duplicate slashes are eliminated. - The presence or absence of a trailing slash in the original path string is carefully respected. Now that we've nailed down how it ought to behave -- added unit tests to ensure that it DOES behave that way!! Change license from GPL to LGPL (version 2.1) 2010-08-13T11:24:57Z Oz Linden oz@lindenlab.com 2010-08-13T11:24:57Z urn:sha1:06b0d72efa96b6a0ed665f7cd46f358c48929e7b DEV-41080 more automated testing love - minor comment fixing. 2009-10-16T12:39:05Z Adam Moss moss@lindenlab.com 2009-10-16T12:39:05Z urn:sha1:e922089ff429cf8f501359fb06761124609caa0e DEV-41352 convert lluri tut test to a llcommon integration test 2009-10-15T18:05:15Z Adam Moss moss@lindenlab.com 2009-10-15T18:05:15Z urn:sha1:986bf99839a79f13a4b16218c221cb123d4bfc15