wsgi proxy and 'hop by hop' about restkit HOT 3 OPEN

The newest HTTP 1.1 rfc versions don't seem to define hop by hop anymore. They used to be in see RFC 2616, section 13.5.1. RFC 7230 section 6.1 does say that a proxy must remove Connection as well as anything listed in the connection header (unless that's close, I guess).

from restkit.

I've investigated this some more, and here are my conclusions:

http://blog.startifact.com/posts/new-http-rfcs-versus-wsgi.html

Until the WSGI pep is updated I think we should just hardcode the list anyway. We know for sure that not removing these headers won't be compatible with a WSGI server. In fact, Waitress just complains when you try to send out Transfer-Encoding to it from a WSGI app.

from restkit.

Now I wonder whether my analysis was correct. Waitress should be able to handle a hop-by-hop header as it's a HTTP server. I think it complains when the underlying WSGI code tries to generate a hop-by-hop header, which is odd because I didn't think we were...

from restkit.