trafficserver-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From cschombu <...@git.apache.org>
Subject [GitHub] trafficserver pull request: TS-4070 RemapProcessor Forward Mapping...
Date Mon, 14 Dec 2015 18:59:17 GMT
GitHub user cschombu opened a pull request:

    https://github.com/apache/trafficserver/pull/375

    TS-4070 RemapProcessor Forward Mapping with Recv Port failing with TS…

    …-2157 changes
    
    During the rework of RemapProcessor.cc, RemapProcessor::setup_for_remap()
    as part of the TS-2157 changeset, the port access API appears to have been
    incorrectly modified to use the client_info.src_addr.host_order_port() API
    [source port, host order] instead of the client_info.dst_addr.port()
    [destination/receive port, network order] API. This caused port based
    remapping based on the receive port to fail with ATS 6.0.0.

You can merge this pull request into a Git repository by running:

    $ git pull https://github.com/cschombu/trafficserver TS-4070

Alternatively you can review and apply these changes as the patch at:

    https://github.com/apache/trafficserver/pull/375.patch

To close this pull request, make a commit to your master/trunk branch
with (at least) the following in the commit message:

    This closes #375
    
----
commit 83851dc1ee5f147024cca3f5129a1d266f273ecd
Author: Craig Schomburg <craigs@cisco.com>
Date:   2015-12-14T18:53:19Z

    TS-4070 RemapProcessor Forward Mapping with Recv Port failing with TS-2157 changes
    
    During the rework of RemapProcessor.cc, RemapProcessor::setup_for_remap()
    as part of the TS-2157 changeset, the port access API appears to have been
    incorrectly modified to use the client_info.src_addr.host_order_port() API
    [source port, host order] instead of the client_info.dst_addr.port()
    [destination/receive port, network order] API. This caused port based
    remapping based on the receive port to fail with ATS 6.0.0.

----


---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not have this feature
enabled and wishes so, or if the feature is enabled but not working, please
contact infrastructure at infrastructure@apache.org or file a JIRA ticket
with INFRA.
---

Mime
View raw message