On Wed, 3 Nov 2004, Frank Neumann wrote:
the vendor of that crazy website tracked that problem and came out with the conclusion that the connection from squid to the website needs to be persistent for the whole conversation.
Sounds like you may experiensing yet another completely broken application which assumes one TCP connection == one client. This assumption is not valid within HTTP.
As squid by default tries to use persistent connections I assume that the website doesn't correctly implement persistence.
Probably.
But since this used to work with squid 2.4.7 (I know that squid 2.5 is more strictly enforcing standards) I've got 2 questions: - What's the difference between squid 2.4 und 2.5 regarding this behaviour?
None that I know of.
- Is there any chance to get this configured to work?
It depends on the nature of the brokenness in the application design.
Regards Henrik
