That is what CONNECT does. Do mean transparently? Maybe fallback on request parse error to bit proxy.
On Nov 2, 2010 12:17 PM, "Alan M. Carroll" <a...@network-geographics.com> wrote: One issue that has come up for us is tolerating network applications that use port 80 for non-HTTP traffic. What is the best way to handle these in ATS, particularly protocols that use HTTP style requests but non-HTTP style responses? Is there already a bypass mechanism in ATS that would cause ATS to simply move bytes without caching between the client and the origin server? Thanks.
