Comments (5)
I just realized that, because this is a new method and will be treated as such by intermediaries that don't understand it, they will pass Datagram-Flow-Id along. That is very much a bad thing as the server on the next hop might have negotiated H3_DATAGRAM with the intermediary for other reasons. If the next hop understands the setting, it might send responses in datagrams that will then be dropped by the intermediary (because it doesn't understand Datagram-Flow-Id).
That is, on a chain of entities from client A, intermediary B, and intermediary C, if all of them support H3_DATAGRAM, but B does not support Datagram-Flow-Id or CONNECT-UDP, this ultimately results in packets being sent on the request stream for a while, then DATAGRAM frames being sent toward the intermediary and being dropped.
from masque-drafts.
Regarding your first comment, I agree that this is somewhat of a hop-by-hop field. Do you have a proposal that achieves the same result without using a hop-by-hop field?
Regarding your second comment, it's not possible for intermediaries to not understand this and still pass it along. If the intermediary doesn't know about this spec it'll respond with status code 405 "Method Not Allowed" instead of forwarding it.
from masque-drafts.
Proxies aren't required to understand all methods, so why would it send a 405? I mean, some might because they want to police what methods they pass, but they are not required to do so.
from masque-drafts.
Sorry, I should have said 501 "Not Implemented", not 405.
from masque-drafts.
This issue has been moved to the official WG repo
from masque-drafts.
Related Issues (20)
- Add more details on negotiation of the listed services HOT 1
- MASQUE application or service? HOT 2
- Don't use .well-known HOT 2
- Securing MASQUE usage from web-based JavaScript HOT 2
- What is the MASQUE POST body content-type HOT 2
- Improve threat model documentation HOT 1
- Rename "validated" in compression contexts HOT 1
- QUIC Proxying needs more explanatory text HOT 1
- QUIC Proxying should better explain compression contexts HOT 1
- CONNECT-UDP and multiple intermediaries HOT 3
- CONNECT-UDP request body HOT 2
- Flow duration HOT 2
- Address mapping and return flow routing HOT 2
- Datagram-Flow-Id size limits HOT 2
- CONNECT-UDP should communicate MTU HOT 2
- CONNECT-UDP needs a request target URI HOT 3
- Editorial: Minor: Spelling error: "probable"
- explicitly state that MASQUE's HTTP CONNECT should reply as if it wasn't there HOT 2
- Transport-Authentication should be a structured header HOT 1
Recommend Projects
-
React
A declarative, efficient, and flexible JavaScript library for building user interfaces.
-
Vue.js
🖖 Vue.js is a progressive, incrementally-adoptable JavaScript framework for building UI on the web.
-
Typescript
TypeScript is a superset of JavaScript that compiles to clean JavaScript output.
-
TensorFlow
An Open Source Machine Learning Framework for Everyone
-
Django
The Web framework for perfectionists with deadlines.
-
Laravel
A PHP framework for web artisans
-
D3
Bring data to life with SVG, Canvas and HTML. 📊📈🎉
-
Recommend Topics
-
javascript
JavaScript (JS) is a lightweight interpreted programming language with first-class functions.
-
web
Some thing interesting about web. New door for the world.
-
server
A server is a program made to process requests and deliver data to clients.
-
Machine learning
Machine learning is a way of modeling and interpreting data that allows a piece of software to respond intelligently.
-
Visualization
Some thing interesting about visualization, use data art
-
Game
Some thing interesting about game, make everyone happy.
Recommend Org
-
Facebook
We are working to build community through open source technology. NB: members must have two-factor auth.
-
Microsoft
Open source projects and samples from Microsoft.
-
Google
Google ❤️ Open Source for everyone.
-
Alibaba
Alibaba Open Source for everyone
-
D3
Data-Driven Documents codes.
-
Tencent
China tencent open source team.
from masque-drafts.