[Wireshark code review <code-review-do-not-reply@xxxxxxxxxxxxx>]

URL: https://code.wireshark.org/review/gitweb?p=wireshark.git;a=commit;h=aecbbb600040b203493d3e896be377b3b4dfd360
Submitter: "Peter Wu <peter@xxxxxxxxxxxxx>"
Changed: branch: master-2.2
Repository: wireshark

Commits:

aecbbb6 by Peter Wu (peter@xxxxxxxxxxxxx):

    HTTP: really choose the correct server port for tunnels
    
    The very first message after a 200 OK response to a CONNECT request
    likely originates from the client. So assume that this destination is
    actually the server.
    
    This reduces the probability of address and port collisions. Previously
    the proxy port (e.g. 3128) and server port (443) identified each
    conversation, now it will use the client and server port instead.
    
    Bug: 15043
    Change-Id: Ib73f370334873efd773ac6b49e2db57146bc20b0
    Fixes: v2.9.0rc0-1420-g2f126db3fe ("HTTP: set correct server port for tunnels")
    Reviewed-on: https://code.wireshark.org/review/29110
    Petri-Dish: Peter Wu <peter@xxxxxxxxxxxxx>
    Tested-by: Petri Dish Buildbot
    Reviewed-by: Anders Broman <a.broman58@xxxxxxxxx>
    (cherry picked from commit 1d4bb22a225285a1fb088d0970499131d242d098)
    Reviewed-on: https://code.wireshark.org/review/29121
    Reviewed-by: Peter Wu <peter@xxxxxxxxxxxxx>
    

Actions performed:

    from  3ccdfbc   [Automatic update for 2018-08-12]
     add  aecbbb6   HTTP: really choose the correct server port for tunnels


Summary of changes:
 epan/dissectors/packet-http.c | 4 ++--
 1 file changed, 2 insertions(+), 2 deletions(-)