You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@trafficserver.apache.org by "Jan-Frode Myklebust (JIRA)" <ji...@apache.org> on 2012/07/10 10:10:34 UTC
[jira] [Updated] (TS-1340) It's very unclear that one needs to list
ipv4 and ipv6 ports separately in records.config
[ https://issues.apache.org/jira/browse/TS-1340?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Jan-Frode Myklebust updated TS-1340:
------------------------------------
Attachment: 0001-Document-the-common-use-case-of-running-a-reverse-pr.patch
Give example of the common use-case of listening on port 80 and 443 for ipv4 and ipv6.
> It's very unclear that one needs to list ipv4 and ipv6 ports separately in records.config
> -----------------------------------------------------------------------------------------
>
> Key: TS-1340
> URL: https://issues.apache.org/jira/browse/TS-1340
> Project: Traffic Server
> Issue Type: Improvement
> Components: Configuration
> Reporter: Jan-Frode Myklebust
> Priority: Trivial
> Attachments: 0001-Document-the-common-use-case-of-running-a-reverse-pr.patch
>
>
> The default records.config should document that one needs to list separate server_ports port configuring ipv4 and ipv6 to get it to listen on both protocols, and not simply list 80:ipv4:ipv6 which the current documentation seems to indicate. I'll attach a patch that gives an example of this for proxy/config/records.config.default.in. Please apply,
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira