[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 ] Uri Shachar updated TS-295: --- Assignee: Uri Shachar > 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: Uri Shachar >Priority: Minor > Fix For: Doc 3.4 > > 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. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira
[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.
[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: - Fix Version/s: (was: 2.1.0) > 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.
[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: - Fix Version/s: 2.2.0 The fix for this is committed to trunk, moving this out to 2.2.0 target for documentation updates. > 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 > Fix For: 2.2.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.
[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: - Assignee: (was: Diane Smith) I'm not sure if Diane will work on Apache TS any more, so moving these back to the unassigned pool. Diane, if you are still interested in working with, by all means please reassign these bugs (and any other bugs) that you wish to work on! > 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 >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. - For more information on JIRA, see: http://www.atlassian.com/software/jira