Viewing profile — lucaspardue

Nice overview! There is a draft [1] that would support Alt-Svc in DNS. Lots to consider there but it is being presented to IETF. [1] - https://tools.ietf.org/html/draft-nygren-dnso…

We use HTTP Alternative Services (RFC 7838). This appears as a Alt-Svc response header that advertises the availability of HTTP/3 to a client. The client uses its local knowledge (…

Multiplexing is beneficial, otherwise we'd never have seen HTTP user agents opening up multiple TCP connections. The gain of moving to binary was the ability to multiplex multiple …

Versions prior to HTTP/2 give the appearance of being simple but in actuality there are many many edge cases that also are the cause of vulnerabilities. HTTP/2's binary syntax addr…

This depends on how the proxy is configured to behave. One common pattern is to have a protocol terminating proxy talk to the client. Other component(s) sit behind this and they co…

These papers are interesting, thanks for sharing. However, the primary axiom is of a web server that is serving static content that is located on the device. That, in a sense, give…

There is still a place for WebSockets in HTTP/2. The fairly recent RFC 8441 defines a mechanism to reserve a single HTTP/2 stream for bidirectional WebSockets. It is feasible for a…

Do you mean forward proxies? The HTTP/3 draft currently specifies how the CONNECT method is used. At present, it only allows you to create an onward TCP connection. So you have a Q…