[
https://issues.apache.org/jira/browse/TS-4615?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15355465#comment-15355465
]
ASF GitHub Bot commented on TS-4615:
------------------------------------
GitHub user jacksontj opened a pull request:
https://github.com/apache/trafficserver/pull/768
TS-4615 set SRV scheme based on next_hop_scheme
You can merge this pull request into a Git repository by running:
$ git pull https://github.com/jacksontj/trafficserver TS-4615
Alternatively you can review and apply these changes as the patch at:
https://github.com/apache/trafficserver/pull/768.patch
To close this pull request, make a commit to your master/trunk branch
with (at least) the following in the commit message:
This closes #768
----
commit b037505a8a09941e5b259f738b4ccc85fb9e1aa4
Author: Thomas Jackson <[email protected]>
Date: 2016-06-29T15:53:04Z
TS-4615 set SRV scheme based on next_hop_scheme
----
> Dynamic SRV lookups
> -------------------
>
> Key: TS-4615
> URL: https://issues.apache.org/jira/browse/TS-4615
> Project: Traffic Server
> Issue Type: Improvement
> Reporter: Thomas Jackson
> Fix For: 7.0.0
>
>
> Right now all SRV lookups are `_http._tcp.NAME`, it'd be better if we
> switched between the various protocols we support (http/https/ws/wss).
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
