Mailing-List: contact dev-help@geronimo.apache.org; run by ezmlm
Precedence: bulk
Reply-To: dev@geronimo.apache.org
Message-ID: <33398184.1199737473893.JavaMail.jira@brutus>
Date: Mon, 7 Jan 2008 12:24:33 -0800 (PST)
From: "Sangjin Lee (JIRA)" <jira@apache.org>
To: dev@geronimo.apache.org
Subject: [jira] Commented: (GERONIMO-3706) support for proxy
In-Reply-To: <28468350.1197647084276.JavaMail.jira@brutus>
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit


    [ https://issues.apache.org/jira/browse/GERONIMO-3706?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12556681#action_12556681 ] 

Sangjin Lee commented on GERONIMO-3706:
---------------------------------------

1) That sounds fine...

2) I'm thinking the following might be a good set (gleaning from various http clients/systems):
- host name (e.g. "www.apache.org")
- domain (e.g. ".apache.org")
- IP address (e.g. "127.0.0.1")
- IP subnet; i.e. IP address + net mask (e.g. "34.56.78.0/255.255.255.192")

I think the first three are critical, but the last is good to have...

3) I think a *single* delimited string would be just fine (e.g. "|" or ";", etc.).  If we force the domain name to start with ".", we can determine whether something is a domain name as opposed to a hostname unambiguously.  I don't think it's critical to have incremental changes to the exclusion list...


One key issue is whether we want to resolve the IP address (or conversely do an ns lookup) when we perform the match.  For example, if "localhost" is specified in the configuration, and the hostname is "127.0.0.1", do we want to match that by performing a lookup, or do we want to force users to specify both forms?

> support for proxy
> -----------------
>
>                 Key: GERONIMO-3706
>                 URL: https://issues.apache.org/jira/browse/GERONIMO-3706
>             Project: Geronimo
>          Issue Type: New Feature
>      Security Level: public(Regular issues) 
>          Components: AsyncHttpClient
>    Affects Versions: 1.x
>            Reporter: Sangjin Lee
>         Attachments: proxy_poc.patch
>
>
> Proxy support is a critical feature for HTTP clients.  I'd like to have AsyncHttpClient support proxy.  The following would be considered as the basic features:
> - Enabling connecting through proxies for http and https targets
> - Exclusion (domains that should not go through proxies)
> - Allowing proxy related configuration on AsyncHttpClient
> - Support for proxy authentication, at least for Basic authentication (and perhaps Digest too?)
> There are things like SOCKS support, etc., but the above will be a good start.  Thoughts?

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