6 commits

Author	SHA1	Message	Date
Daniel Stenberg	b5593a6fe0	urlapi: use uppercase hex encoding ... For consistency. RFC 3986 section 2.1 says: "URI producers and normalizers should use uppercase hexadecimal digits for all percent-encodings." Reported-by: Jeroen Ooms Fixes #17685 Closes #17739	2025-06-25 11:44:13 +02:00
Nigel Brittain	c19465ca55	http_aws_sigv4: improve sigv4 url encoding and canonicalization ... Closes #17129	2025-05-21 08:07:18 +02:00
Maksim Ściepanienka	235b575d3a	tests: add aws feature to the related tests ... Closes #17347	2025-05-14 23:41:38 +02:00
Daniel Stenberg	11cad7bf32	tests: provide all non-ascii data hex encoded ... - make the scanner not whitelist anything for test cases making everything non-ascii forced to be hex encoded - update all tests using non-ascii bytes to use %hex[] sequences Closes #17331	2025-05-13 10:32:35 +02:00
Viktor Szakats	18f1cd7a77	tests: sync feature names with curl -V ... Some feature names used in tests had minor differences compared to the well-known ones from `curl -V`. This patch syncs them to make test results easier to grok. Closes #14183	2024-07-16 00:44:55 +02:00
Matthias Gatto	768909d89c	aws-sigv4: url encode the canonical path ... Refactors canon_query, so it could use the encoding part of the function to use it in the path. As the path doesn't encode '/', but encode '=', I had to add some conditions to know If I was doing the query or path encoding. Also, instead of adding a `bool in_path` variable, I use `bool *found_equals` to know if the function was called for the query or path, as found_equals is used only in query_encoding. Test 472 verifies. Reported-by: Alexander Shtuchkin Fixes #13754 Closes #13814 Signed-off-by: Matthias Gatto <matthias.gatto@outscale.com>	2024-05-29 13:02:52 +02:00