bryancall commented on issue #11900: URL: https://github.com/apache/trafficserver/issues/11900#issuecomment-4828270474
Thanks for the detailed write-up. After reading through the thread, this is standard YAML behavior rather than an inconsistency in Traffic Server. In your example, `local_ipv6: [2601:282:4300:54:4d17:e14a:9a32:b49d]` is wrapped in square brackets, and YAML reads bracketed text as a flow sequence (an array), so the scalar-to-string conversion fails with "bad conversion". The `outgoing_ip_to_bind` value parsed fine only because it was written without brackets and without a trailing colon or other YAML indicator character. As maskit noted, you would get the same error on `outgoing_ip_to_bind` if it were written the same way. Both fields are read identically as plain strings (`RecGetRecordStringAlloc` for `proxy.config.dns.local_ipv4` and `local_ipv6` in `src/iocore/dns/DNS.cc`), so there is no field-specific parsing difference in Traffic Server. The correct approach is exactly what you landed on: quote any value that contains YAML indicator characters, for example `local_ipv6: "2601: 282:4300:54:4d17:e14a:9a32:b49d"` (no brackets). Since the question has been answered and the workaround is the expected usage, I am closing this. Please reopen if you hit a case that does not fit the YAML rules above. -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. To unsubscribe, e-mail: [email protected] For queries about this service, please contact Infrastructure at: [email protected]
