> I had a similar problem for one of our sites. Looks like you are behind a > firewall. Read and try a combination of > > never_direct > always_direct > > parameters to get to your sites without timing out. > Wouldn't I then have to build a list of *all* websites that use source IP as session identifiers? How does the always_direct work? I presume it doesn't build a tunnel for the client to host communications? In which case I'd have the same problem :( > Faisal > -----Original Message----- > From: Nick Bryant [mailto:list@xxxxxxxxxxxxxxxxxxxxxx] > Sent: Wednesday, August 24, 2005 3:51 AM > To: squid-users@xxxxxxxxxxxxxxx > Subject: Problems with sites that use sessions > > Hi, > > I'm having a few issues with sites that use sessions going through our > squid > (2.5.STABLE3). > > Basically all works well until a session gets set and then the site will > come up with a "Your Session has timed out" type message, irrelevant from > the type of site being used. It doesn't always happen but I'd say it's > more > often than not. However, un-setting the proxy in the browser seems to > resolve the issue every time. For an example that doesn't require a login, > check out www.lastminute.com.au > > Has anyone experienced anything similar? Can anyone give me any clues as > to > what I can look at in the config? > > TIA > > N > > > __________ NOD32 1.1200 (20050823) Information __________ > > This message was checked by NOD32 antivirus system. > http://www.eset.com
