[jira] Commented: (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:comment-tabpanel&focusedCommentId=12929666#action_12929666 ] 

Leif Hedstrom commented on TS-295:
----------------------------------

Further additions / comments on the docs changes:

The old setting for proxy.config.http.ssl_ports is gone, and replaced with proxy.config.http.connect_ports. This new setting has nothing to do with SSL, other than it defaults to two common SSL ports. What the setting really does it do tell the server (TS) what destination ports clients are allowed to CONNECT to (tunneling). This new configuration supports both wildcards ('*') and ranges ("0-1023").


> 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
>          Components: Documentation
>    Affects Versions: 2.0.0
>         Environment: All?
>            Reporter: Marcus Clyne
>            Assignee: Diane Smith
>            Priority: Minor
>             Fix For: 3.0
>
>         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.