On Mon, Jan 28, 2019 at 9:22 AM Stefan Eissing <stefan.eiss...@greenbytes.de> wrote:
> The HTTP Workshop is returning 2019 on April 2-4 in Amsterdam ( > https://github.com/httpworkshop/workshop2019). While I attended the last > three shops(?), I think it would be a good opportunity for someone else > from the team to go there and meet some smart and friendly people from the > HTTP world. > I found Daniel's blogs on the last (2017) meetup very helpful for context; https://daniel.haxx.se/blog/2017/06/12/http-workshop-london-edition-first-day/ https://daniel.haxx.se/blog/2017/06/13/http-workshop-s03e02/ It seems there is little retrospective of HTTP/1.1, while challenges/footnotes to h2 and tls1.3 will be discussed, and waka (would be good to hear an update from Roy on this) and quik seem to still be the primary topics of the day. So someone interested in writing the HTTP/3 implementation for httpd would be the obvious choice of delegate. (Hoping Roy already plans to attend.) One issue that has reared its ugly head again and again for us is URL conformance and ambiguity, and especially early decoding of % escapes (and non-normative %U escapes that may try to pass through proxies.) Since there was discussion of completely refactoring URL encoding/decoding patterns in httpd 3.0, someone interested in proceeding on that work would make a helpful workshop liason. Another issue of interest is bidirectional and push content, which the httpd core largely ignores but could better support. Although that's probably off in the weeds for browser and middle-tier folks. The usefulness of 100-Continue through proxies and mis-interpretations of the spec on this might be interesting conversation. The HTTP WS organisers expressed the wish to have someone from "Apache" > present. Anyone interested? Could also be someone from another HTTP related > Apache project, of course. > It seems TrafficServer is already in the loop, as Leif attended last time. Tomcat is an obvious gap, cc'ed. Also seems that Tatsuhiro is in the loop, having attended in 2016 and being key to httpd's support of h2 protocol. It might be that the HTTP/3 .. quik implementation, if httpd gains one, ultimately looks like mod_h2, a layer over another's implementation.