[jira] Assigned: (TS-295) Allowing HTTP CONNECT to be used on non-SSL ports

["Leif Hedstrom (JIRA)" <ji...@apache.org>]

     [ https://issues.apache.org/jira/browse/TS-295?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Leif Hedstrom reassigned TS-295:
--------------------------------

    Assignee: Diane Smith  (was: Leif Hedstrom)

Hi Diane,

Can you take this bug, and update the documentation? This feature adds a new option

   CONFIG proxy.config.http.connect_ports STRING  port1 port2 ...


The default is 443 and  563. The purpose of this setting is to restrict which ports a client is allowed to CONNECT to on the remote side. Connect is a generic tunneling method in HTTP, and is typically used to tunnel HTTPS, but can be used for any HTTP port.

Before this change, CONNECT had the same restriction on ports as proxy.config.http.ssl_ports, but this is now decoupled. The usage of ssl_ports has not changed.

> Allowing HTTP CONNECT to be used on non-SSL ports
> -------------------------------------------------
>
>                 Key: TS-295
>                 URL: https://issues.apache.org/jira/browse/TS-295
>             Project: Traffic Server
>          Issue Type: Improvement
>    Affects Versions: 2.0.0
>         Environment: All?
>            Reporter: Marcus Clyne
>            Assignee: Diane Smith
>            Priority: Minor
>         Attachments: TS-295.diff
>
>
> Currently HTTP CONNECT can only be used on ports designated as SSL ports in the config file, even if SSL is not used.
> It seems more sensible to add a config option to specify which ports can be tunneled through using CONNECT's, perhaps defaulting to the SSL ports, but not being limited to them.

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