Dan Romero
@dwr.eth
Anyone excited about HTTP SEARCH? https://httptoolkit.com/blog/http-search-method/
5 replies
2 recasts
7 reactions
Danny
@ds
Not very exciting. GET is pretty close, and many proxies will happily send the body upstream… not GCP load balancers though. So you can’t totally rely on that. It seems like if you actually need this you could use a header to change POST behavior at the cache layer.
0 reply
0 recast
0 reaction
n64jerry
@n64jerry
having a use case / decision making convo with GPT-4 was helpful to better understand when to go with HTTP SEARCH vs a GraphQL query exciting stuff - thanks for sharing 💖
0 reply
0 recast
0 reaction
Russell Castagnaro
@rcastag
It definitely could make server logs more useful!
0 reply
0 recast
0 reaction
timdaub
@timdaub.eth
so this is graphql standardized?
0 reply
0 recast
0 reaction
0xAndrew
@0xandrew
Pretty cool. But working in crypto, all of the APIs that I write are read only. Writes are sent as transactions through their wallet, not the API, so I'm already treating POST requests as if they were GET requests with a body, which seems to me like the TLDR of what SEARCH is trying to accomplish
0 reply
0 recast
0 reaction