this post was submitted on 17 Sep 2024
32 points (100.0% liked)

Web Development

3425 readers
3 users here now

Welcome to the web development community! This is a place to post, discuss, get help about, etc. anything related to web development

What is web development?

Web development is the process of creating websites or web applications

Rules/Guidelines

Related Communities

Wormhole

Some webdev blogsNot sure what to post in here? Want some web development related things to read?

Heres a couple blogs that have web development related content

CreditsIcon base by Delapouite under CC BY 3.0 with modifications to add a gradient

founded 1 year ago
MODERATORS
top 6 comments
sorted by: hot top controversial new old
[–] Deebster@programming.dev 6 points 2 days ago* (last edited 2 days ago) (3 children)

Makes a lot of sense - it's a GET with the body from POST (I know, there's more to it than that). Definitely cleaner than encoding a huge URL or query string.

However, we're still implementing IPv6, so how long until we could actually use this?

[–] frezik@midwest.social 4 points 1 day ago

I haven't read through the whole spec to know what else is there, but the thing is, HTTP/1.1 always allowed GET to have a body. It was originally supposed to be ignored, but they gave up on that later on because it's dumb.

https://stackoverflow.com/a/983458

[–] DacoTaco@lemmy.world 3 points 1 day ago

If i was in control, rather quickly haha

[–] lysdexic@programming.dev 3 points 2 days ago (1 children)

However, we’re still implementing IPv6, so how long until we could actually use this?

We can already use custom verbs as we please: we only need to have clients and servers agree on a contract.

What we don't have is the benefit of high-level "batteries included" web frameworks doing the work for us.

[–] Deebster@programming.dev 1 points 1 day ago (1 children)

What about proxies and the like? It might be less relevant in a world where most communication happens under TLS.

[–] lysdexic@programming.dev 3 points 1 day ago

Custom methods won't have the benefit of being dealt with as if they shared specific semantics, such as being treated as safe methods or idempotent, but ultimately that's just an expected trait that anyone can work with.

In the end, specifying a new standard HTTP method like QUERY extends some very specific assurances regarding semantics, such as whether frameworks should enforce CRSF tokens based on whether a QUERY has the semantics of a safe method or not.