These are chat archives for cherrypy/cherrypy
CherryPy is a pythonic, object-oriented HTTP framework. | post your issues to: github.com/cherrypy/cherrypy/issues | FAQ: https://stackoverflow.com/questions/tagged/cheroot+or+cherrypy
CONNECTis just a reserved method, so there's no explicit rules for processing it, which is probably the reason why routing worked in old implementation and the request reached appropriate handler.
CONNECTis specified as a method for establishing TCP tunnel through HTTP proxy (specifically for SSL/TLS connections).
CONNECT example.com:3128 HTTP/1.1is valid (it instructs web proxy to establish connection to host example.com port 3128 and forward there and back all the traffic from the client through existing connection).
CONNECT http://example.com:3128 HTTP/1.1,
CONNECT /some/path HTTP/1.1,
CONNECT example.com HTTP/1.1are all invalid and should return 400
405 Method Not Allowedunless the appropriate extension/module is enabled
it’s not attempting to implement RFC7231
Yes, but it's trying to implement RFC7230, section 5.3.3, which restricts request-target to match authority-form, meaning we cannot consume any URI path information from the request, but rather return error if it's there.