trafficserver-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "George Paul (JIRA)" <j...@apache.org>
Subject [jira] Commented: (TS-291) Enable transparent forward proxying
Date Fri, 09 Apr 2010 16:40:50 GMT

    [ https://issues.apache.org/jira/browse/TS-291?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12855466#action_12855466
] 

George Paul commented on TS-291:
--------------------------------

For Issue 1, see section '14.23 Host' in the  HTTP/1.1 RFC specification  (http://www.w3.org/Protocols/rfc2616/rfc2616-sec14.html)
for handling of "Host" field header. 

For Issue 2 you can safely assume that 'transparency_enabled' variable was used for indicating
'transparent forward proxy' mode AFAIR.

-George

> Enable transparent forward proxying
> -----------------------------------
>
>                 Key: TS-291
>                 URL: https://issues.apache.org/jira/browse/TS-291
>             Project: Traffic Server
>          Issue Type: Improvement
>          Components: Network
>         Environment: Linux
>            Reporter: Alan M. Carroll
>            Priority: Minor
>
> Currently ATS provides only explicit forward proxying. It should support this transparently
as well.
> Transparent means
> * No configuration on clients.
> * Origin server sees the client IP address as the source address of the cache fill request.
> This should be an option set via configuration variables because transparent proxying
is not always the correct mode of operation. In addition, it requires a Linux kernel with
TPROXY support and so will not run in all environments.

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.


Mime
View raw message