jeredfloyd commented on PR #12338: URL: https://github.com/apache/trafficserver/pull/12338#issuecomment-3220611284
@maskit I generally agree with your analysis, but I think parallel functionality already exists with `@in_ip` which is why I propose `@in_proto` as a different implementation. It's possible that I'm misunderstanding what the current functionality does and these filters do not allow for overloading of targets? From https://docs.trafficserver.apache.org/en/latest/admin-guide/files/remap.config.en.html examples: ``` map http://foo.example.com/ http://foo.example.com/ @action=allow @src_ip=10.5.2.1 @in_ip=72.209.23.4 ``` So I propose: ``` map http://foo.example.com/ http://origin-unix.example.com/ @action=allow @in_proto=unix map http://foo.example.com/ http://origin-http.example.com/ @action=allow @in_proto=http ``` If that doesn't actually work the way I think I'll stop arguing, but I do think the above is a much cleaner abstraction as it does not create non-standard URIs. -- 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: github-unsubscr...@trafficserver.apache.org For queries about this service, please contact Infrastructure at: us...@infra.apache.org
