geronimo-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Rick McGuire (JIRA)" <>
Subject [jira] Commented: (GERONIMO-3706) support for proxy
Date Thu, 03 Jan 2008 10:16:33 GMT


Rick McGuire commented on GERONIMO-3706:

Your proof of concept looks very nice.  I've scrapped the work I had started and am going
to use your proof of concept for the base implementation.  I have a few questions on how to
proceed from here.

1)  The JVM deployment properties file allows configuring a different host/port for http and
https?  I suspect that may be desired here, with the default to use the same for both. 

2)  There seems not to be a lot of consistency in the format of the exclusion lists and the
level of wildcarding supported between the JRE and the different browsers.  Right now, I'm
going for a combination of exact domain matches and a leading wildcard (e.g., *

3)  How should the exclusion list be specified?  A delimited string like is set in
 A List of domains?  Both/either?  Should the exclusion list allow incremental additions/deletions?

> support for proxy
> -----------------
>                 Key: GERONIMO-3706
>                 URL:
>             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
> 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.

View raw message