0xEAB commented on issue Handy-Http/primitives#3 2024-10-28 23:02:29 +00:00
Client address

(Another minor issue is that unions aren’t accessible in @safe code.)

Given that this library already uses std.typecons, would it be acceptable to use std.sumtype for the implementation…

0xEAB commented on issue Handy-Http/primitives#3 2024-10-28 22:52:45 +00:00
Client address

It would mean that each request takes up an additional 16 bytes for the request, but I prefer this over the polymorphic class-based approach in Phobos.

Yeah, I don’t think we have to go…

0xEAB commented on issue Handy-Http/primitives#2 2024-10-28 22:21:33 +00:00
Request query parameter storage

So you're suggesting that the ServerHttpRequest simply provides the full raw URL, and that users would be free to parse it however they like?

Yeah. Sounds like the most flexible approach to me.

0xEAB commented on issue Handy-Http/primitives#4 2024-10-27 16:41:47 +00:00
HTTP version of requests and TLS

As-is, it cannot properly do so for v1.0 and v0.9 requests.

As servers usually reply to such with v1.1 responses anyway, I guess it would be sufficient to rename V1_1 to V1 and document…

0xEAB opened issue Handy-Http/primitives#4 2024-10-27 16:39:28 +00:00
HTTP version of requests and TLS
0xEAB opened issue Handy-Http/primitives#3 2024-10-27 16:19:08 +00:00
Client address
0xEAB commented on issue Handy-Http/primitives#1 2024-10-27 15:52:53 +00:00
Support for arbitrary HTTP methods

The HttpStatus enum, on the other hand, already contains WebDAV status codes, like <23c74f82be/source/h

0xEAB opened issue Handy-Http/primitives#2 2024-10-27 15:45:11 +00:00
Request query parameter storage
0xEAB opened issue Handy-Http/primitives#1 2024-10-27 15:24:48 +00:00
Support for arbitrary HTTP methods