i�ve encountered strange problems using squid as proxy together with the Oracle Application Server, but let me short explain:
The application itself is an ERP-application developed with Oracle Forms and Runtimes (which ran originally in client/server-mode). Later on Oracle developed the so called "Application Server" which is just an Apache with an JServ-Module for presenting the Forms in the clients web browser. On Client-Side runs the Internet Explorer with the so called Oracle JInitiator (basically an java runtime environment).
The connection between client and application server uses the http-protocol.
Here we come to my problem:
I�ve tested various combinations for making the application itself available over my companys wan-network (basically isdn and vpn-connections) to our customers. If i am using plain tcp/ip+http i can see with ethereal two tcp connections to the application server (good). But i want to integrante completely into our present infrastructure: All customers are forced to connect over an squid 2.5.5-2 proxy for security and access restriction reasons. So i�ve tested squid as proxy in this environment.
Firstly i used squid 2.5.4 (from debian testing) which showed > 135 tcp connections (it seemed keep-alive is not working properly; i will come to that) and a _extremely_ bad performance. After upgrading to squid 2.5.5 the amount of connections doesnt changed but the performance increased by factor four (why ??). If i am using squid 2.4.6 from Debian Stable i have only 2 tcp-connection (like the two i had when using plain tcp/ip as mentioned befotre).
So i need to know what changed between 2.5.4 and 2.5.5 and what changed between 2.4.6 and 2.5.5.
Thanks, Ronny.
