These are chat archives for cherrypy/cherrypy

25th
Nov 2018
Ian Otto
@duper51
Nov 25 2018 03:20
I noticed you may have wanted to totally defer parsing to another library, is that something you're very interested in?
I might be able to put in the work for that.
Sviatoslav Sydorenko
@webknjaz
Nov 25 2018 15:47
do you mean hyper?
Ian Otto
@duper51
Nov 25 2018 18:25
Yeah
Sviatoslav Sydorenko
@webknjaz
Nov 25 2018 21:23
It's not well-thought yet. That's just an idea for now. I'd focus on completion of existing PR, it looks safer. I was thinking to experiment with hyper after polishing existing change. Do you think you could try to poke on it?
Ian Otto
@duper51
Nov 25 2018 22:30
Yeah, what exactly are you looking over the existing commit?
Sviatoslav Sydorenko
@webknjaz
Nov 25 2018 22:31
If I recall correctly after reconsideration I've decided that I wasn't sure I correctly got how to process proxy (connect?) case from RFC
So at first this needs a validation against RFC
which is very time-consuming (RFCs are hard and sometimes misleading)
Ian Otto
@duper51
Nov 25 2018 22:40
I'll poke around and see what we can see
Sviatoslav Sydorenko
@webknjaz
Nov 25 2018 22:40
cool! that'd be lovely
Ian Otto
@duper51
Nov 25 2018 23:16
Just looking over the RFC, I would say we error out with a
400 status, since the request is technically malformed/incomplete. That said it looks like that's require a downstream change for cherrypy since we use proxy mode there? I'm currently trying to read through the docs
That is for proxy_mode only though. The current change should be valid for when that isn't set