[jira] [Commented] (TS-1001) reload the changes in dns.resolv_conf
[ https://issues.apache.org/jira/browse/TS-1001?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13135778#comment-13135778 ] Zhao Yongming commented on TS-1001: --- I think we need more input on how to handle config file monitoring, as commented in TS-1003, we many need to do some more change to handle config file register in server runtime. > reload the changes in dns.resolv_conf > - > > Key: TS-1001 > URL: https://issues.apache.org/jira/browse/TS-1001 > Project: Traffic Server > Issue Type: Wish > Components: DNS >Reporter: Conan Wang >Priority: Trivial > > a trivial wish: ATS can reload (traffic_line -x) resolv.conf if nameserver > changed. -- 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
[jira] [Commented] (TS-1001) reload the changes in dns.resolv_conf
[ https://issues.apache.org/jira/browse/TS-1001?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13135813#comment-13135813 ] Conan Wang commented on TS-1001: I mean manually reload the resolv_conf. ATS cannot reload that currently. > reload the changes in dns.resolv_conf > - > > Key: TS-1001 > URL: https://issues.apache.org/jira/browse/TS-1001 > Project: Traffic Server > Issue Type: Wish > Components: DNS >Reporter: Conan Wang >Priority: Trivial > > a trivial wish: ATS can reload (traffic_line -x) resolv.conf if nameserver > changed. -- 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
[jira] [Created] (TS-1004) transformation plugins cause connection close when content length is not known ahead
transformation plugins cause connection close when content length is not known ahead Key: TS-1004 URL: https://issues.apache.org/jira/browse/TS-1004 Project: Traffic Server Issue Type: Bug Components: HTTP, Plugins Affects Versions: 3.0.1 Reporter: Otto van der Schaaf whenever the null transform plugin (or gzip) is executed, ATS will force the ua connection closed. when the user agent supports it, sending a chunked response w/ keepalive enabled would be preferred i guess i'll add a patch for review. -- 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
[jira] [Updated] (TS-1004) transformation plugins cause connection close when content length is not known ahead
[ https://issues.apache.org/jira/browse/TS-1004?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Otto van der Schaaf updated TS-1004: Attachment: chunk_transform_response.diff > transformation plugins cause connection close when content length is not > known ahead > > > Key: TS-1004 > URL: https://issues.apache.org/jira/browse/TS-1004 > Project: Traffic Server > Issue Type: Bug > Components: HTTP, Plugins >Affects Versions: 3.0.1 >Reporter: Otto van der Schaaf > Attachments: chunk_transform_response.diff > > > whenever the null transform plugin (or gzip) is executed, ATS will force the > ua connection closed. > when the user agent supports it, sending a chunked response w/ keepalive > enabled would be preferred i guess > i'll add a patch for review. -- 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
