fang 14266c8d46 eyre: GETting non-existent channels 404s ... Contrary to the argument made by 4affae8, this is the _actually correct_ behavior. Not creating server-side resources in response to GETs respects the expected method semantics, and more importantly, serving a 404 is an important signal for clients trying to connect to a channel they were using previously. Without that, they have no way of telling whether, when reconnecting, if their channel was reaped in the mean time or not. The "empty PUT" affordance provided by 34148f9 makes requiring a PUT request for channel creation more reasonable. We leave the general refactoring done by #6789 in place, but do emphasize the reasoning given here with a few additional comments.		2023-10-04 22:42:50 +02:00
..
arvo	tests: move to root, out of pkg/arvo	2023-01-18 16:50:42 +01:00
hoon	test: adds failing multi-byte-glyph sanity	2023-05-31 14:32:39 -04:00
vane	eyre: GETting non-existent channels 404s	2023-10-04 22:42:50 +02:00
zuse	Merge branch 'next/kelvin/413' into i/5788/remote-scry	2023-04-22 14:33:20 -04:00
fine.hoon	Merge branch 'next/kelvin/412' into tinnus/local-provenance	2023-06-07 20:38:05 +12:00
grq.hoon	tests: revert test now that dead flow consolidation is default off	2023-09-14 23:13:24 +03:00
nock.hoon	tests: move to root, out of pkg/arvo	2023-01-18 16:50:42 +01:00