Commit Graph

244 Commits

Author SHA1 Message Date
e6634d3c0f
shell32 has been removed, use USERPROFILE env var instead
Some checks failed
aws-zig mach nominated build / build-zig-nightly (push) Failing after 1h21m14s
aws-zig nightly build / build-zig-nightly (push) Failing after 10m24s
2024-04-02 11:05:17 -07:00
7dcf3d3a2e
upgrade to nominated zig 2024.3.0-mach (0.12.0-dev.3180+83e578a18)
Some checks failed
aws-zig mach nominated build / build-zig-nightly (push) Failing after 28m36s
aws-zig nightly build / build-zig-nightly (push) Failing after 57s
There were significant changes to the way HTTP operates since 0.11,
effecting client operations, but more substantially, the server
implementation, which effected the test harness.

std.http.Headers was removed, including the getFirstValue function, which
needed to be replicated. On the plus side, a std.http.Header struct was
added, identical to our own structure, so I have removed out own header
in favor of stdlib.

On the Http client side, I have switched to use the fetch API. Proxy
support is built in, but we are using (mostly) our own implementation
for now, with the remaining conversion left as a TODO item. Raw URIs are
now supported, so the workaround for issue 17015 has been removed. Large
payloads should also be fixed, but this has not been tested.

The standard library now adds the content-length header
(unconditionally), which is a decision of dubious nature. I have removed
the addition of content-length, which also means it is not present
during signing. This should be allowed.

Dependency loop on fieldTransformer was fixed. This should have been
a problem on zig 0.11, but was not. This effected the API for the json
parsing, but we were not using that. At the call site, these did not
need to be specified as references.

With the http server no longer doing all the allocations it once was,
the test harness now has a lot more allocations to perform. To alleviate
the bookeeping, this was moved to an Arena allocator. The client,
which is really what is under test, continues to use the allocator
passed.
2024-04-02 09:27:42 -07:00
6df02b1074
switch sqs query test (json) with sts query test (xml) and fix response parsing
All checks were successful
AWS-Zig Build / build-zig-0.11.0-amd64-host (push) Successful in 5m22s
2024-02-29 20:41:03 -08:00
55298f7575
skip sqs, which changed from query to json protocol, and update S3 test
All checks were successful
AWS-Zig Build / build-zig-0.11.0-amd64-host (push) Successful in 4m18s
2024-02-29 16:59:10 -08:00
31324c7e83
support for server verification of clients that do not pass x-amz-content-sha256
All checks were successful
AWS-Zig Build / build-zig-0.11.0-amd64-host (push) Successful in 5m17s
2024-02-24 09:43:36 -08:00
melhindi
7a5fa0bb2e Replace var with const where applicable
All checks were successful
AWS-Zig Build / build-zig-0.11.0-amd64-host (push) Successful in 7m37s
2024-01-18 13:43:45 +01:00
14666da73f
clean up build (includes two fixes for arm 32 bit)
All checks were successful
AWS-Zig Build / build-zig-0.11.0-amd64-host (push) Successful in 5m38s
2024-01-09 15:22:03 -08:00
d08d0f338f
Using ".?" actually causes a panic, which we do not want in this path
All checks were successful
AWS-Zig Build / build-zig-0.11.0-amd64-host (push) Successful in 7m20s
NOTE: This only fixes the top level Authorization header. A malformed
header can still cause havoc
2023-10-25 00:00:11 -07:00
825d93720a
add verifiyServerRequest/change verify to WASM-friendly type
All checks were successful
AWS-Zig Build / build-zig-0.11.0-amd64-host (push) Successful in 8m20s
2023-10-22 10:25:07 -07:00
ed96e2ff66
support for >16KiB requests
All checks were successful
AWS-Zig Build / build-zig-0.11.0-amd64-host (push) Successful in 7m44s
2023-10-21 10:20:09 -07:00
db19041b96
fix memory leak when AWS_ENDPOINT_URL is used
All checks were successful
AWS-Zig Build / build-zig-0.11.0-amd64-host (push) Successful in 7m4s
2023-09-15 09:05:53 -07:00
f8b6b3e521
make aws_signing module ready 2023-09-14 14:06:35 -07:00
ff1e6f4cf3
aws_signing: provide signing verification based on a server http request
All checks were successful
AWS-Zig Build / build-zig-0.11.0-amd64-host (push) Successful in 7m41s
2023-09-08 21:45:36 -07:00
0e48c6f79b
clean up test logging/add header logging in test 2023-09-08 21:43:20 -07:00
6ae8b68786
allow static signing iime in aws.zig/use static time for testing 2023-09-08 21:42:38 -07:00
037fb7f1ae
allow aws_http to use static signing time 2023-09-08 21:41:08 -07:00
fd0e80f00c
allow datetime to timestamp conversion from outside date.zig 2023-09-08 21:40:03 -07:00
67b24641e2
allow trailing Z on iso 8601 parsing 2023-09-08 21:39:19 -07:00
2d42bbf464
comment date logging functions so type can be used at comptime 2023-09-08 21:38:28 -07:00
6755099c36
apparently we do need that check?
All checks were successful
AWS-Zig Build / build-zig-0.11.0-amd64-host (push) Successful in 7m36s
2023-08-30 13:49:56 -07:00
fb34e556f7
re-enable demo code 2023-08-30 13:49:29 -07:00
d82728602b
fix failing test 2023-08-30 13:40:08 -07:00
d50503a2f8
initial commit on code to work around 17015. Sourced from std lib 2023-08-30 13:32:27 -07:00
55f662f5d7
add failing test for double encoding issue 2023-08-30 12:59:10 -07:00
f2a3a967c7
add comment to indicate root cause of the tagResource issue 2023-08-30 12:55:40 -07:00
c011f1d7f9
update user agent (we have not used AWS Common Runtime for a while 2023-08-30 12:55:06 -07:00
8926fd439e
clean up response code output 2023-08-30 12:54:35 -07:00
1376a7f898
indicate that test is being skipped and why 2023-08-30 12:53:42 -07:00
88c8643eb3
fix url encoding early out 2023-08-29 15:21:47 -07:00
993f9cd91c
allow -vvv as option on demo 2023-08-29 15:21:15 -07:00
9c403d0e18
cleanup output/remove one demo due to signature issue
All checks were successful
AWS-Zig Build / build-zig-0.11.0-amd64-host (push) Successful in 6m11s
2023-08-29 12:47:22 -07:00
316a388b79
support chunked encoding (but not streaming really) 2023-08-29 12:36:18 -07:00
0a1de2b967
support chunked transfer encoding to create failing test 2023-08-29 11:56:23 -07:00
70bd8dafa5
add more information on unexpected response 2023-08-29 11:56:01 -07:00
48fc41c4b8
return cleaner error when response not expected 2023-08-29 11:30:21 -07:00
bd72bbb1f3
clean up output (first pass) 2023-08-29 11:29:50 -07:00
9d7df078b0
0.11 now looks for std_options decl in root 2023-08-29 11:29:16 -07:00
812ad96a66
add proxy support 2023-08-29 11:24:34 -07:00
58949127d6
add help to demo program 2023-08-29 07:26:11 -07:00
591f4c43e0
all services from main.zig now under test
All checks were successful
AWS-Zig Build / build-zig-0.11.0-amd64-host (push) Successful in 6m28s
2023-08-28 17:49:30 -07:00
71978e2386
add comment in demo on TLS v1.3 situation 2023-08-28 16:42:43 -07:00
a8dddfbd30
update readme and talk about TLS 1.3 (sigh)
All checks were successful
AWS-Zig Build / build-zig-0.11.0-amd64-host (push) Successful in 6m59s
2023-08-28 14:25:59 -07:00
c8cba54fe0
ec2_query_with_input under test
All checks were successful
AWS-Zig Build / build-zig-0.11.0-amd64-host (push) Successful in 7m9s
2023-08-28 13:30:39 -07:00
6d3e820bd1
add ec2_query_no_input 2023-08-28 13:10:16 -07:00
eafb62aee9
fix leaks/re-enable rest_json_1 tests
All checks were successful
AWS-Zig Build / build-zig-0.11.0-amd64-host (push) Successful in 6m28s
2023-08-28 12:37:34 -07:00
827c90ab8a
add rest json tests (skippped -still leaky
All checks were successful
AWS-Zig Build / build-zig-0.11.0-amd64-host (push) Successful in 5m15s
2023-08-27 23:20:07 -07:00
034172c7b3
progress indicator on main 2023-08-27 23:18:55 -07:00
1b2b51be88
fix path not added on override 2023-08-27 23:18:15 -07:00
c39fc940b9
fix map pattern in zig 0.11 2023-08-27 23:07:35 -07:00
edf931f827
add json_1_1_query_no_input: ecs listClusters runtime
All checks were successful
AWS-Zig Build / build-zig-0.11.0-amd64-host (push) Successful in 5m16s
2023-08-27 21:53:39 -07:00