-
Notifications
You must be signed in to change notification settings - Fork 276
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
http: Removes section about http paths #636
base: master
Are you sure you want to change the base?
Conversation
We have a multiaddr for `/http-path` so the section is now irrelevant
@@ -13,13 +13,13 @@ Interest Group: [@marcopolo], [@mxinden], [@marten-seemann] | |||
[@marten-seemann]: https://github.com/marten-seemann | |||
|
|||
## Table of Contents <!-- omit in toc --> | |||
|
|||
- [Context](#context) | |||
- [What is an HTTP transport](#what-is-an-http-transport) | |||
- [Multiaddr representation](#multiaddr-representation) | |||
- [HTTP Paths (and other HTTP Semantics)](#http-paths-and-other-http-semantics) |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
This TOC line needs removing since the corresponding section has been removed, or you can regenerate it using Markdown All in One or similar.
|
||
Note: When we use `/quic-v1/http` or `/tcp/443/tls/http` (or any other | ||
transport) implementations MUST use the correct HTTP ALPN (e.g. `h3` or `h2` | ||
respectively) and not `libp2p` when using the HTTP transport. | ||
|
||
## HTTP Paths (and other HTTP Semantics) | ||
|
||
It may be tempting to add an HTTP path to end of the multiaddr to specify some |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I guess this means we do have paths in HTTP Multiaddrs now? Is it worth adding an example of their use?
We have them now.