[jbosstools-issues] [JBoss JIRA] (JBIDE-26452) Explore existing proxy server set up solutions outside RH - proxy requirements definition

[Ondrej Dockal (Jira)]

    [ https://issues.jboss.org/browse/JBIDE-26452?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13657506#comment-13657506 ] 

Ondrej Dockal edited comment on JBIDE-26452 at 2/17/19 1:29 PM:
----------------------------------------------------------------

Tinyproxy - https://tinyproxy.github.io/:
* HTTP/S
* GPLv2
* github: https://github.com/tinyproxy/tinyproxy
* github issues tracker
* written in c
* last commit Dec 2018
* can be used
* Not yet verified
* active community


was (Author: odockal):
Tinyproxy - https://tinyproxy.github.io/:
* HTTP/S
* GPLv2
* github: https://github.com/tinyproxy/tinyproxy
* github issues tracker
* written in c
* last commit Sep 2018
* can be used
* Not yet verified
* active community

> Explore existing proxy server set up solutions outside RH - proxy requirements definition
> -----------------------------------------------------------------------------------------
>
>                 Key: JBIDE-26452
>                 URL: https://issues.jboss.org/browse/JBIDE-26452
>             Project: Tools (JBoss Tools)
>          Issue Type: Task
>          Components: integration-tests, qa
>    Affects Versions: 4.10.0.AM1
>         Environment: Linux
>            Reporter: Ondrej Dockal
>            Assignee: Ondrej Dockal
>            Priority: Major
>              Labels: quality
>             Fix For: 4.11.0.AM1
>
>
> Explore existing solutions for proxy configuration that could be done at one step without requiring deep user knowledge.
> Existing docker images with squid (other?) proxy. Licensing, usage within RH intranet. Is there an open source code? 
> Requirements for proxy solution: 
> * Supports HTTP and HTTPS protocols
> * Clear and configurable logging and other tools
> * runs on linux
> * Open Source solution
> * License usable "in house" (can be use for profit = in enterprise environment)
> * Project is alive/maintained - or we would must maintain our own fork?
> * Community 
> * Code on github - preferably
> * uses issue tracking system
> Requirements for putting proxy into action:
> * easy to deploy solution
> * does not require user knowledge of proxy configuration - minimalist config
> * can be updated at place 
> * RH certificate can be used



--
This message was sent by Atlassian Jira
(v7.12.1#712002)