Yes, transparently would be preferred. I am not sure what you mean by "CONNECT", though -- is that a state in the HTTP SM? Does ATS already have a bit proxy? I have glanced at the blind tunnel logic but not investigated it. I am mainly looking for hints as to what part of the code I should be investigating in this regard.
Tuesday, November 2, 2010, 7:36:38 PM, you wrote: > 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.
