You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@trafficserver.apache.org by "Alan M. Carroll" <am...@network-geographics.com> on 2010/09/03 04:56:01 UTC
TS-291, transparent forward proxy, first patch merged to trunk
I did a rebase and merge from the ts-291 branch, which had the changes to implement forward transparent proxy (see TS-291). It has had some testing, but not extensive. For this reason it was not included in the 2.1.2 release. However, because that has now been released it seemed a good time to push this non-trivial change to trunk.
Re: TS-291, transparent forward proxy, first patch merged to trunk
Posted by "Alan M. Carroll" <am...@network-geographics.com>.
Friday, September 3, 2010, 1:43:17 PM, you wrote:
> On 09/03/2010 12:17 PM, Leif Hedstrom wrote:
>>> Hmmm, I tried this a little bit, with and without --enable-tproxy=no,
>>> and it works fine with forward proxy, but nothing works in reverse
>>> proxy. I did a complete fresh build / install, modified
>>> records.config to use port 80, and added this to remap.config:
>>> map http://loki.ogre.com/ http://someorigin.com
I am trying to get a test setup working to look in to this problem.
Re: TS-291, transparent forward proxy, first patch merged to trunk
Posted by Leif Hedstrom <zw...@apache.org>.
On 09/03/2010 12:17 PM, Leif Hedstrom wrote:
> On 09/03/2010 12:16 PM, Leif Hedstrom wrote:
>> On 09/02/2010 08:56 PM, Alan M. Carroll wrote:
>>> I did a rebase and merge from the ts-291 branch, which had the
>>> changes to implement forward transparent proxy (see TS-291). It has
>>> had some testing, but not extensive. For this reason it was not
>>> included in the 2.1.2 release. However, because that has now been
>>> released it seemed a good time to push this non-trivial change to
>>> trunk.
>>>
>>
>> Hmmm, I tried this a little bit, with and without --enable-tproxy=no,
>> and it works fine with forward proxy, but nothing works in reverse
>> proxy. I did a complete fresh build / install, modified
>> records.config to use port 80, and added this to remap.config:
>>
>> map http://loki.ogre.com/ http://someorigin.com
>>
>
> I should say, this is just an example, I'm not using "someorigin.com"
> obviously, I just didn't want to expose the real origin server here in
> the email, since I use one on the interweb.
Doing some quick debugging, it seems like it's trying to connect back to
itself, e.g.
[Sep 3 12:36:17.745] Server {140386788771600} DEBUG: (http_track) entered inside do_http_server_open
[Sep 3 12:36:17.745] Server {140386788771600} DEBUG: (http) [0] open connection to loki.ogre.com: 192.168.201.14
[Sep 3 12:36:17.745] Server {140386788771600} DEBUG: (http_seq) [HttpSM::do_http_server_open] Sending request to server
[Sep 3 12:36:17.745] Server {140386788771600} DEBUG: (http) calling netProcessor.connect_re
[Sep 3 12:36:17.745] Server {140386788771600} DEBUG: (http) [0] [HttpSM::main_handler, NET_EVENT_OPEN]
[Sep 3 12:36:17.745] Server {140386726496016} DEBUG: (http_tproxy) Marking accepted connect on 32f81e0 as not outbound transparent.
[Sep 3 12:36:17.745] Server {140386788771600} DEBUG: (http_track) entered inside state_http_server_open
where I'd really expect it to do something like the below (hostname
changed to be the "fake" one to avoid giving it out in email).
[Sep 3 12:37:55.805] Server {140243282487056} DEBUG: (http_track) entered inside do_http_server_open
[Sep 3 12:37:55.805] Server {140243282487056} DEBUG: (http) [0] open connection to www.someorigin.com: 66.66.66.66
[Sep 3 12:37:55.805] Server {140243282487056} DEBUG: (http_seq) [HttpSM::do_http_server_open] Sending request to server
[Sep 3 12:37:55.805] Server {140243282487056} DEBUG: (http) calling netProcessor.connect_re
[Sep 3 12:37:55.842] Server {140243282487056} DEBUG: (http) [0] [HttpSM::main_handler, NET_EVENT_OPEN]
[Sep 3 12:37:55.842] Server {140243282487056} DEBUG: (http_track) entered inside state_http_server_open
[Sep 3 12:37:55.842] Server {140243282487056} DEBUG: (http) [0] [&HttpSM::state_http_server_open, NET_EVENT_OPEN]
loki.ogre.com is the host running ATS, and I'm obviously not expecting
it to proxy back to itself. The second trace above is using the same
config, but the v2.1.2 binary (without tproxy patches), which works.
Cheers,
-- leif
Re: TS-291, transparent forward proxy, first patch merged to trunk
Posted by Leif Hedstrom <zw...@apache.org>.
On 09/03/2010 12:16 PM, Leif Hedstrom wrote:
> On 09/02/2010 08:56 PM, Alan M. Carroll wrote:
>> I did a rebase and merge from the ts-291 branch, which had the
>> changes to implement forward transparent proxy (see TS-291). It has
>> had some testing, but not extensive. For this reason it was not
>> included in the 2.1.2 release. However, because that has now been
>> released it seemed a good time to push this non-trivial change to trunk.
>>
>
> Hmmm, I tried this a little bit, with and without --enable-tproxy=no,
> and it works fine with forward proxy, but nothing works in reverse
> proxy. I did a complete fresh build / install, modified
> records.config to use port 80, and added this to remap.config:
>
> map http://loki.ogre.com/ http://someorigin.com
>
I should say, this is just an example, I'm not using "someorigin.com"
obviously, I just didn't want to expose the real origin server here in
the email, since I use one on the interweb.
-- Leif
Re: TS-291, transparent forward proxy, first patch merged to trunk
Posted by Leif Hedstrom <zw...@apache.org>.
On 09/02/2010 08:56 PM, Alan M. Carroll wrote:
> I did a rebase and merge from the ts-291 branch, which had the changes to implement forward transparent proxy (see TS-291). It has had some testing, but not extensive. For this reason it was not included in the 2.1.2 release. However, because that has now been released it seemed a good time to push this non-trivial change to trunk.
>
Hmmm, I tried this a little bit, with and without --enable-tproxy=no,
and it works fine with forward proxy, but nothing works in reverse
proxy. I did a complete fresh build / install, modified records.config
to use port 80, and added this to remap.config:
map http://loki.ogre.com/ http://someorigin.com
A request for this now always fails with "404":
loki (12:12) 499/0 $ curlhead http://loki.ogre.com/500.bmp | head -1
HTTP/1.1 404 Not Found on Accelerator
Am I missing something ? I've tested with v2.1.2 (works fine) and also
rolling back to before this merge (also works fine).
-- Leif