You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@trafficserver.apache.org by "Leif Hedstrom (JIRA)" <ji...@apache.org> on 2010/05/06 21:40:48 UTC
[jira] Updated: (TS-295) Allowing HTTP CONNECT to be used on
non-SSL ports
[ https://issues.apache.org/jira/browse/TS-295?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Leif Hedstrom updated TS-295:
-----------------------------
Attachment: TS-295.diff
Proposed patch. This adds a new configuration, e.g.
CONFIG proxy.config.http.connect_ports STRING 80 443
Can you please test the attached patch? It's diffed against current "trunk".
> 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: Leif Hedstrom
> Priority: Minor
> Fix For: 2.1.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.