maskit commented on PR #12338: URL: https://github.com/apache/trafficserver/pull/12338#issuecomment-3215947812
@jeredfloyd Thank you for your comment. If we were introducing remap.yaml and we could do completely different things, I'd like the idea of a separate matching parameter. However, remap ACL or `@something` on remap rules is not really an option for this, because `@something` is not a part of a matching pattern. Those are more like actions used after matching. Remap rules work like "If a request matches with this pattern, apply this ACL, and run these plugins". If the ACL deny the access, it results in a 403 response and that's it. That is not what I want at a minimum. In my use case, both entry points (ip and unix socket) are valid, and I want to have different plugin configurations on those remap rules. I read the long discussion on WHATWG, and the scheme idea made most sense to me. I think their discussion was much more complicated than this discussion because they were thinking of standardizing it. Although we should try to stick with standards as much as possible, what I'm proposing is just an application specific format for a config file, and I suppose many libraries can still parse or generate the URL-ish matching pattern string. Also, client applications are not required to do anything special. Requests made by curl command with --unix-path option matches with the rules. For your last point, as you already found, `map_with_recv_port` does the work. I used it on the example in the description. That keyword is the way to remap based on received interface/port. With `remap_with_recv_port`, the remap processor takes received interface/port in consideration, and users need to tell on their remap rules which interface/port to compare with. -- 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
