askiiart/askiiart-net
1
0
Fork 0
Code Issues Pull requests Projects Releases Packages Wiki Activity Actions

Add 300 addendum

Browse source
This commit is contained in:
askiiart 2023-12-06 12:55:40 -06:00
parent 5cfac7a2a3
commit 2e508dc78f
Signed by untrusted user who does not match committer: askiiart
GPG key ID: BC3800E55FB54D67
8 changed files with 113 additions and 11 deletions
Download patch file Download diff file Expand all files Collapse all files

6
blog/300.md
View file

@ -84,9 +84,11 @@ These still don't work, they just return my reverse proxy container's gateway's
Turns out might be a standard way to do it! From [RFC 9110](https://httpwg.org/specs/rfc9110.html#status.300), again:
> It is possible to communicate the list using a set of Link header fields [RFC5988](https://httpwg.org/specs/rfc9110.html#RFC8288), each with a relationship of "alternate", though deployment is a chicken-and-egg problem.
> It is possible to communicate the list using a set of Link header fields *[RFC5988](https://httpwg.org/specs/rfc9110.html#RFC8288)*, each with a relationship of "alternate", though deployment is a chicken-and-egg problem.
I'll probably figure out the `Link` header some other time and will add this later, at which point I'll post an addendum. Until then, bye I guess!
~~I'll probably figure out the `Link` header some other time and will add this later, at which point I'll post an addendum. Until then, bye I guess!~~
Update: `Link` addendum [here](/blog/300-link-addendum.html)!
## Footnotes and stuff