Lars Hupel wrote: > > Current behavior is correct. The first one is what should be sent. > > [...] > > Actually it is helpful. It says that *the resource being requested as > > obtained from the original URI given by the user* is what should be > > sent. This is the "remote" parameter and nothing else. > > So what you're implying is that if a request is sent, the part after > 'CONNECT' must be always the same as the part after 'Host'.
Yep. It's a bit redundant, but consider that CONNECT is already the odd kid among the HTTP verbs. Most other verbs only take an absolute path URI, without host component. > > I'll ack your patch if it only adds a Host header where one is > > missing, and sends the correct contents, ie. the "remote" hostname. > > Hopefully the attached patch is acceptable for you. I'm just another community member, but I think the patch is correct. Thanks! Acked-by: Peter Stuge <pe...@stuge.se>
pgpqMNObQRJv_.pgp
Description: PGP signature